Bug 5797 - Allow native library in class library
Summary: Allow native library in class library
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild (show other bugs)
Version: 4.2.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Atsushi Eno
URL:
Depends on:
Blocks:
 
Reported: 2012-06-21 06:56 UTC by Sebastian Krysmanski
Modified: 2013-07-18 09:51 UTC (History)
3 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Sebastian Krysmanski 2012-06-21 06:56:37 UTC
It should be possible to add a native library (VS Build Action: AndroidNativeLibrary) to an "Android Class Library" project.

You can do this with MfA 4.2 but the library can't be found by P/Invoke when doing this. So, currently the native library must be located in executable/main project.
Comment 1 Atsushi Eno 2013-05-22 17:00:12 UTC
It is now supported in 4.6 and 4.7.x (AndroidNativeLibrary in 4.6, plus EmbeddedNativeLibrary in 4.7.x).
Comment 2 Goncalo Oliveira 2013-07-18 05:20:33 UTC
This doesn't work on 4.6.08007 (0cc7ae3b). The build action is there but the library can't be found by P/Invoke. Only works if the native library is included in the main project.
Comment 3 Atsushi Eno 2013-07-18 09:51:14 UTC
You need to use EmbeddedNativeLibrary in library project if you do not want to include it in the main project. If you do understand that and still believe it doesn't work, please provide a reproducible project that "should" work.

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.