search

kewur / assimp-net

Automatically exported from code.google.com/p/assimp-net
0 stars 0 forks source link

Follow NuGet native package conventions for unmanaged dependencies #31

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Currently the Assimp32.dll and Assimp64.dll native libraries are included in 
the "lib" folder of the NuGet package. This folder is reserved for managed 
assemblies to be included as references (see: 
http://docs.nuget.org/create/creating-and-publishing-a-package#from-a-convention
-based-working-directory)

A more natural place to include these native dependencies would be 
"build\native\bin" with subfolders "x86" (or "Win32") and "x64". The ".targets" 
file can easily be modified to accomodate this. This is the approach used by 
CoApp for example: http://blogs.techsmith.com/inside-techsmith/nuget-packages-3/

This would make AssimpNET play better with other external tools such as testing 
frameworks, frameworks, etc and avoid the creation of unnecessary adapter NuGet 
packages.

Thanks!

Original issue reported on code.google.com by goncaloc...@gmail.com on 30 Jun 2015 at 8:26