Skip to content
⌘ NSIS Forum Archive

Looking for run-time and dev library install documentation

4 posts

seasoned_geek#

Looking for run-time and dev library install documentation

All,

I haven't scoured through everything yet. Will continue digging through the CMake documentation because I think I just need to tweak some things in the install() statements for goodness to happen. Hoping someone here can point me to straightforward documentation on creating
  1. a run-time only installer that just installs libraries
  2. A development installer that installs supporting binaries, libraries, CMake files, documentation, etc.
There's gotta be something simple like additional Component on install


to cause CPack to generate this. Just need a link to doc that explains this briefly
Anders#
You might have better luck asking cmake people. I can only answer NSIS specific questions...
seasoned_geek#
Well this is NSIS specific. I have everything built and placed pretty much where I want it in a release tree. I don't generally do Windows development. For my DEB and RPM packaging of this it is simple. I build into a release directory tree via CMake then have a shell script which pulls out what I need for just a runtime and packages it; then it pulls out what is needed for _DEV package and packages it.

So, for the sake of this discussion ass-u-me

Release-build-dir
Program Files
MyGuiLibrary
bin
lib
include
doc
cmake
share

spewed out the end of the CMake build process because that's how I roll everywhere else

The runtime windows installer should have
Program Files
lib
(maybe bin if we are forcing DLLs there, but none of the executables)
doc (for the licenses)
share


The development package should have everything

What I cannot see is how to tell NSIS to generate those installation packages

All of the doc and examples I can find are "how to bundle your program with the DLLs it needs" which ain't this.

Thanks
Anders#
You have two options.

You can put everything in one installer and by default not install the dev stuff unless the user checks a checkbox. In NSIS, this would be a components page and at least two Section's. This is probably possible with cmake and makes sense if the dev files are small or compress well.

Or if you want two different .exe files, use !ifdef MYDEVSTUFF to only include the dev files in one of them. Compile twice, once with Makensis -DMYDEVSTUFF mysetup.nsi.