On 02/28/2012 05:53 PM, Eric Noulard wrote:
2012/2/28 Andrea Crottiandrea.crott...@gmail.com:
On 02/28/2012 03:42 PM, Eric Noulard wrote:
Yes more or less beside the fact is CPack is doing more work than that:
1) CPack handles CPack-private install location for you
(including the
On Wed, Feb 29, 2012 at 1:44 PM, Andrea Crotti
andrea.crott...@gmail.com wrote:
On 02/28/2012 05:53 PM, Eric Noulard wrote:
2012/2/28 Andrea Crottiandrea.crott...@gmail.com:
On 02/28/2012 03:42 PM, Eric Noulard wrote:
Yes more or less beside the fact is CPack is doing more work than that:
Alright moving the include after did the trick, I get my code in the
final nsi file, as below:
set(CPACK_NSIS_EXTRA_INSTALL_COMMANDS
PageEx directory
DirVar PythonDir
PageExEnd
CreateShortCut \\\$DESKTOP${PROJECT_NAME}.lnk\\\
\\\$INSTDIRbuilt_eggrun.exe\\\
2012/2/28 Andrea Crotti andrea.crott...@gmail.com:
Alright moving the include after did the trick, I get my code in the final
nsi file, as below:
set(CPACK_NSIS_EXTRA_INSTALL_COMMANDS
PageEx directory
DirVar PythonDir
PageExEnd
CreateShortCut
On 02/28/2012 03:42 PM, Eric Noulard wrote:
At worst is there a way to just create my own .nsi file and use it directly?
I need to create a page which simply asks for a directory to the user, and
then use that to create a shortcut..
Any idea (also other solutions might be fine).
1) Copy the
My brain is almost going to explode, so before it does maybe someone can
help..
I have a cpack with NSIS working installer, which just copies a directory.
In that directory there is a file run.exe, which needs to take an
argument to run correctly.
Now that argument is a path which is only
On 02/27/2012 03:34 PM, Andrea Crotti wrote:
My brain is almost going to explode, so before it does maybe someone
can help..
I have a cpack with NSIS working installer, which just copies a
directory.
In that directory there is a file run.exe, which needs to take an
argument to run correctly.
By the way, how do I see the actual paths NSI configuration that generates
the final exe?
It seems that if NSIS works the file used get all removed..
It does not get removed for me using Visual Studio 2010. All of the
NSIS stuff exists in a _CPack_Packages folder inside of the build
tree.
On 02/27/2012 04:52 PM, John Drescher wrote:
By the way, how do I see the actual paths NSI configuration that generates
the final exe?
It seems that if NSIS works the file used get all removed..
It does not get removed for me using Visual Studio 2010. All of the
NSIS stuff exists in a
Ah yes you're right, last time I checked I didn't see them..
Anyway my extra_commands don't appear anywhere in the nsi file, is that
normal?
I can't help with that part. I do add components also executables with
shortcuts for my executables by setting the CPACK_PACKAGE_EXECUTABLES
variable.
2012/2/27 John Drescher dresche...@gmail.com:
Ah yes you're right, last time I checked I didn't see them..
Anyway my extra_commands don't appear anywhere in the nsi file, is that
normal?
No i'ts not.
Did you set(CPACK_NSIS_EXTRA_INSTALL_COMMANDS ...)
BEFORE
include(CPack) ?
The process is
On 02/27/2012 05:51 PM, Eric Noulard wrote:
2012/2/27 John Drescherdresche...@gmail.com:
Ah yes you're right, last time I checked I didn't see them..
Anyway my extra_commands don't appear anywhere in the nsi file, is that
normal?
No i'ts not.
Did you set(CPACK_NSIS_EXTRA_INSTALL_COMMANDS ...)
12 matches
Mail list logo