Chiebot-Mirror
/
protobuf
mirror of https://github.com/protocolbuffers/protobuf.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
11524 Commits
197 Branches
346 Tags
251 MiB
Tag: Branch: Tree: 23.x-202305051714
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '23.x-202305051714'
${ noResults }
protobuf/csharp/Google.Protobuf.Tools.nuspec

39 lines
2.3 KiB
Raw Permalink Normal View History Unescape

Replace update_version shell script with a python script, which is much better at handling XML rewrite. Update the PHP version too. As part of rewrite, some XML file format will change a little, but the semantics is still the same so it should be okay.
6 years ago
<?xml version="1.0" encoding="UTF-8"?>
Introduce a new nuget package, Google.Protobuf.Tools, basically to contain protoc on multiple platforms. I've moved both protoc.exe and the proto files out of Google.Protobuf. The .proto files aren't a slam-dunk, but it feels like they belong with protoc as you'd *use* them with protoc. It's not clear to me whether we really need both an x86 and x64 version of protoc.exe, as x86 would work on 64-bit Windows anyway. Discuss :)
9 years ago
<package>
<metadata>
<id>Google.Protobuf.Tools</id>
<title>Google Protocol Buffers tools</title>
<summary>Tools for Protocol Buffers - Google's data interchange format.</summary>
<description>See project site for more info.</description>
Updating version.json and repo version numbers to: 23.0-rc3
2 years ago
<version>3.23.0-rc3</version>
Introduce a new nuget package, Google.Protobuf.Tools, basically to contain protoc on multiple platforms. I've moved both protoc.exe and the proto files out of Google.Protobuf. The .proto files aren't a slam-dunk, but it feels like they belong with protoc as you'd *use* them with protoc. It's not clear to me whether we really need both an x86 and x64 version of protoc.exe, as x86 would work on 64-bit Windows anyway. Discuss :)
9 years ago
<authors>Google Inc.</authors>
<owners>protobuf-packages</owners>
Replace master with main in URLs & docs
3 years ago
<licenseUrl>https://github.com/protocolbuffers/protobuf/blob/main/LICENSE</licenseUrl>
Replace repo links.
6 years ago
<projectUrl>https://github.com/protocolbuffers/protobuf</projectUrl>
Introduce a new nuget package, Google.Protobuf.Tools, basically to contain protoc on multiple platforms. I've moved both protoc.exe and the proto files out of Google.Protobuf. The .proto files aren't a slam-dunk, but it feels like they belong with protoc as you'd *use* them with protoc. It's not clear to me whether we really need both an x86 and x64 version of protoc.exe, as x86 would work on 64-bit Windows anyway. Discuss :)
9 years ago
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<releaseNotes>Tools for Protocol Buffers</releaseNotes>
<copyright>Copyright 2015, Google Inc.</copyright>
<tags>Protocol Buffers Binary Serialization Format Google proto proto3</tags>
</metadata>
<files>
Use forward slash instead of backslash in nuspec file (#11449) We are going to pack this on a linux machine now, so we need to use forward slashes. Closes #11449 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11449 from protocolbuffers:deannagarcia-patch-16 24a4ecfc85f4a008a807cab89ea1a54ea68ab77e PiperOrigin-RevId: 499512069
2 years ago
<file src="protoc/windows_x86/protoc.exe" target="tools/windows_x86/protoc.exe"/>
<file src="protoc/windows_x64/protoc.exe" target="tools/windows_x64/protoc.exe"/>
<file src="protoc/linux_x86/protoc" target="tools/linux_x86/protoc"/>
<file src="protoc/linux_x64/protoc" target="tools/linux_x64/protoc"/>
<file src="protoc/macosx_x64/protoc" target="tools/macosx_x64/protoc"/>
Change nuspec configuration's proto file path. The ../ was causing an error in how the targets were being copied over. Since we have to copy the files anyway, it doesn't matter where we expect the files. PiperOrigin-RevId: 503259682
2 years ago
<file src="src/google/protobuf/any.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/api.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/descriptor.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/duration.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/empty.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/field_mask.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/source_context.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/struct.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/timestamp.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/type.proto" target="tools/google/protobuf"/>
<file src="src/google/protobuf/wrappers.proto" target="tools/google/protobuf"/>
Replace update_version shell script with a python script, which is much better at handling XML rewrite. Update the PHP version too. As part of rewrite, some XML file format will change a little, but the semantics is still the same so it should be okay.
6 years ago
<file src="Google.Protobuf.Tools.targets" target="buildCrossTargeting"/>
<file src="Google.Protobuf.Tools.targets" target="build"/>
Introduce a new nuget package, Google.Protobuf.Tools, basically to contain protoc on multiple platforms. I've moved both protoc.exe and the proto files out of Google.Protobuf. The .proto files aren't a slam-dunk, but it feels like they belong with protoc as you'd *use* them with protoc. It's not clear to me whether we really need both an x86 and x64 version of protoc.exe, as x86 would work on 64-bit Windows anyway. Discuss :)
9 years ago
</files>
Make sure to add a new line at the end of XML files
6 years ago
</package>