This is useful when the package is hosted in, you can do a search for native packages by using the search term: tag:nativeĮach xml element has two attributes: a ‘src’ attribute and a ‘target’ attribute. To be doubly sure I got it right, I added it twice, the first time with a capital ‘N’. The most important part here is the element that contains the text ‘native’. I chose to have the package contents follow the same layout as how Google gives them to me.
For my example, mine is filament.nuspec:Ī nuspec files is an xml file and hence must follow the syntax requirements as documented on microsoft’s website:
That makes it easier and simplifies the paths we will put inside the *.nuspec file. I like to put this *.nuspec file inside of the directory that has the code I’m packaging up. This should be easy, copy all the files you need for your native library to a a convenient folder. NOTE: In this document I will be using the Google Filament renderer library as my demonstration example, since I had to do that here at work recently.
Edit the visual studio project file to point to where the restored nuget package is.Push the nuget package to a feed somewhere.Edit the *.nuspec file to include the files you want to include in your package.Gather or stage your native library files into a folder of your choosing.Here is a high-level summary of what needs to be done, and will be explained in detail: It is up to you to break open your text editor and modify your visual studio project files (*.vcxproj etc.). The third key is that none of the Visual Studio versions will offer any aid at all in hooking up the nuget package to the project that needs it. The second key is that we will just be using Nuget to download and unzip the nuget package for us. Therefore you should just be able to stick anything in there that you like. The first key to understand how to put C++ stuff into a nuget package is to understand that a nuget package (*.nupkg) is really just a zip file that has been renamed. Making a nuget package for managed code is really straightforward, since it is so extensively documented on Microsoft’s various websites.īut if you want to make a nuget package that contains native code like libraries (*.lib), headers (*.h) you are almost out of luck! Microsoft will give you about 3 minuscule paragraphs full of cryptic junk for documentation!
0 kommentar(er)
