Skip to content

Conversation

@jonpryor
Copy link
Contributor

@jonpryor jonpryor commented Aug 9, 2016

Update the make jenkins target to package up the bin directory for
(hopeful) use on other machines.

The generated package is named:

oss-xamarin-android,branch=BRANCH,commit=COMMIT,version=VERSION.zip

where BRANCH is the git branch being built (usually master), COMMIT
is the git commit that was built, and VERSION contains the new
$(ProductVersion) MSBuild property along with the number of commits
since $(ProductVersion) was changed.

The package file is not an installer, just a ZIP package, but should
contain everything needed to create an installer.

@jonpryor jonpryor force-pushed the jonp-zip-output branch 2 times, most recently from cb878ae to e714a6c Compare August 9, 2016 19:01
@grendello
Copy link
Contributor

grendello commented Aug 9, 2016

Should the package name contain the OS name and the OS architecture?

Update the `make jenkins` target to package up the `bin` directory for
(hopeful) use on other machines.

The generated package is named:

	oss-xamarin-android_vVERSION_OS-ARCH_BRANCH_COMMIT.zip

where:

* **VERSION** is the new `$(ProductVersion)` MSBuild property
    along with the number of commits since `$(ProductVersion)`
    was *changed*
* **OS** is the name of the OS that built the package
* **ARCH** is the OS architecture
* **BRANCH** is the git branch being built (usually `master`)
* **COMMIT** is the git commit that was built.

For example:

	oss-xamarin.android_v7.0.99.0_Darwin-x86_64_jonp-zip-output_c4eab00.zip

The package file is *not* an installer, just a ZIP package, but should
contain everything needed to *create* an installer.

This also copies `tools/scripts/xabuild` into the appropriate
`bin/$(Configuration)/bin` directories so that an `xabuild` script is
installed as part of the package, and `xabuild` is updated to setup
the various environment variables accordingly so it is invokable from
the `bin/$(Configuration)/bin` directories.
@grendello grendello merged commit 1eebbe3 into dotnet:master Aug 9, 2016
radekdoulik pushed a commit to radekdoulik/xamarin-android that referenced this pull request Aug 12, 2016
Update the `make jenkins` target to package up the `bin` directory for
(hopeful) use on other machines.

The generated package is named:

	oss-xamarin-android_vVERSION_OS-ARCH_BRANCH_COMMIT.zip

where:

* **VERSION** is the new `$(ProductVersion)` MSBuild property
    along with the number of commits since `$(ProductVersion)`
    was *changed*
* **OS** is the name of the OS that built the package
* **ARCH** is the OS architecture
* **BRANCH** is the git branch being built (usually `master`)
* **COMMIT** is the git commit that was built.

For example:

	oss-xamarin.android_v7.0.99.0_Darwin-x86_64_jonp-zip-output_c4eab00.zip

The package file is *not* an installer, just a ZIP package, but should
contain everything needed to *create* an installer.

This also copies `tools/scripts/xabuild` into the appropriate
`bin/$(Configuration)/bin` directories so that an `xabuild` script is
installed as part of the package, and `xabuild` is updated to setup
the various environment variables accordingly so it is invokable from
the `bin/$(Configuration)/bin` directories.
radical pushed a commit that referenced this pull request May 8, 2018
… ones. (#153)

There are classes that implement more than one interfaces that share an
identical methods (which share the same name and the same JNI signature).
For example, java.nio.AsynchronousFileChannel implements Closeable and
AsynchronousChannel, both of which contain `close()` method.

Only one `Close()` should be generated for that class.
jonpryor added a commit to jonpryor/xamarin-android that referenced this pull request Feb 17, 2022
Context: dotnet/android-tools#156

Changes: jonpryor/xamarin-android-tools@0e80ea1...9768b42

  * jonpryor/xamarin-android-tools@9768b42: [Xamarin.Android.Tools.AndroidSdk] Update SDK component for API-32
  * dotnet/android-tools@a7f4d30: [ci] Mention new NuGet feed and release (dotnet#153)
  * dotnet/android-tools@85ae77f: Merge pull request dotnet#152 from xamarin/dev/mattnorflus/SigningMigration
  * dotnet/android-tools@dd34e54: Adding condition to GetFilesToSign to only include files if build configuration is Release
jonpryor added a commit to jonpryor/xamarin-android that referenced this pull request Feb 18, 2022
Context: dotnet/android-tools#156

Changes: jonpryor/xamarin-android-tools@0e80ea1...9768b42

  * jonpryor/xamarin-android-tools@9768b42: [Xamarin.Android.Tools.AndroidSdk] Update SDK component for API-32
  * dotnet/android-tools@a7f4d30: [ci] Mention new NuGet feed and release (dotnet#153)
  * dotnet/android-tools@85ae77f: Merge pull request dotnet#152 from xamarin/dev/mattnorflus/SigningMigration
  * dotnet/android-tools@dd34e54: Adding condition to GetFilesToSign to only include files if build configuration is Release
jonpryor added a commit to jonpryor/xamarin-android that referenced this pull request Feb 18, 2022
Changes: jonpryor/xamarin-android-tools@0e80ea1...bbe85df

  * dotnet/android-tools@bbe85df4: [Xamarin.Android.Tools.AndroidSdk] Update SDK component for API-32
  * dotnet/android-tools@a7f4d30: [ci] Mention new NuGet feed and release (dotnet#153)
  * dotnet/android-tools@85ae77f: Merge pull request dotnet#152 from xamarin/dev/mattnorflus/SigningMigration
  * dotnet/android-tools@dd34e54: Adding condition to GetFilesToSign to only include files if build configuration is Release
jonpryor added a commit that referenced this pull request Feb 18, 2022
Changes: jonpryor/xamarin-android-tools@0e80ea1...bbe85df

  * dotnet/android-tools@bbe85df4: [Xamarin.Android.Tools.AndroidSdk] Update SDK component for API-32
  * dotnet/android-tools@a7f4d30: [ci] Mention new NuGet feed and release (#153)
  * dotnet/android-tools@85ae77f: Merge pull request #152 from xamarin/dev/mattnorflus/SigningMigration
  * dotnet/android-tools@dd34e54: Adding condition to GetFilesToSign to only include files if build configuration is Release
@github-actions github-actions bot locked and limited conversation to collaborators Feb 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants