On 02/26/2012 11:24 AM, Alexander Neundorf wrote:
> On Sunday 26 February 2012, Michael Hertling wrote:
>> On 02/25/2012 09:43 AM, Alexander Neundorf wrote:
>>> On Friday 24 February 2012, Michael Hertling wrote:
On 02/24/2012 03:34 PM, Stephen Kelly wrote:
>>> ...
>>>
>> [...] (that is, f
2012/2/27 Mauricio Klein :
> Hello everybody!
>
> I'm creating a NSIS package using CPack to install my software.
>
> The code is compilled using Visual Studio 9, and the compilation + packing
> is working well.
>
> But, once i install the software using the generated NSIS package, the
> program do
On 02/27/2012 05:51 PM, Eric Noulard wrote:
2012/2/27 John Drescher:
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
Actually I
2012/2/27 John Drescher :
>> 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 relatively simpl
> 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.
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 _CPack_Pa
> 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 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.
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 known
Thanks Michael
The behaviour I was asking about is resolved. At some point in my
CMakeFiles.txt, it didn't work for my user on MacOSX, but apparently it does
work now, so I (or he) must have had another mistake in the files earlier
on. But you have made some helpful suggestions, so my comments are
> In order to maximize our ability to rebuild an exact copy of a previous
> revision, our repository carries copies of numerous 3rd party libraries.
>
> However, in most of their cases we are fairly selective about which
> elements we build.
>
> Downside: "make clean && make" winds up rebuilding al
11 matches
Mail list logo