Mark,
One of the difficulties with converting our file to an NSIS template was
getting around which variables in the template are done by directly
substituting variables from the CMake file and which ones are done via the
generator. In particular, the generator was causing me the biggest issues.
Rick,
Okay.
The configure_file() command looks promising. That's what I was trying to
do yesterday by using a NSIS.template.in file that was a copy of our old
oorexx.nsi file and just have variables for the /D options. But, it didn't
work at all.
--
Mark Miesfeld
On Mon, Jun 9, 2014 at
Yeah, configure_file() is a useful command. I'm actually making good
progress with this (in stages). My current plan is to generate include
files for both the component file manifests and the shortcuts (the
shortcuts are done). This will all get created in build directory, the
.nsi file well
On Mon, Jun 9, 2014 at 7:29 AM, Rick McGuire object.r...@gmail.com wrote:
btw, do we still need the isNT tests in the .nsi file? We can eliminate
one include file if those are no longer needed.
We don't really need it. But, if we remove it, the section for setting the
path needs to be
I did this in then nsis template file...it was a pretty easy change.
Rick
On Monday, June 9, 2014, Mark Miesfeld miesf...@gmail.com wrote:
On Mon, Jun 9, 2014 at 7:29 AM, Rick McGuire object.r...@gmail.com
javascript:_e(%7B%7D,'cvml','object.r...@gmail.com'); wrote:
btw, do we still need
Sorry I wasn't engaged in this topic earlier. But, I don't agree with the
approach we've taken with this.
We have a perfectly good NSIS script that produces the NSIS installer on
Windows. This script has been refined over the years until it is at the
point it is today.
I think we should just
Ok, I guess I'm good with that. Since we need to tweak this a bit, I
suggest we leave oorexx.nsi unchanged and check in a new file to build from
(and I agree, a custom script might not be a bad idea). A batch file is a
good idea here, although I wonder if we can add a to the cmake script that
is
Mark,
I was right, it was pretty easy to add this as a build target (assuming I
got the command syntax right). To build the installer, just issue the
command nmake nsis_installer from the build directory command line. This
is setup with dependencies on the doc files being in an indicated
Mark,
I've been poking around, and it might actually be possible to still drive
the install from CMake and still keep the current installer. I've how to
get access to the install information and it should be possible to inject
that information into a template install file. This is something for
Hi Rick,
I just made a couple of small changes and your custom target now works.
I don't think I have an objection to using the CPack version.
Earlier today, I was thinking we could drive the installer creation from
CPack by just using a NSIS.template.in file that was a copy of our current
10 matches
Mail list logo
