The variable is set bevor include(CPack) and the generated nsi file
locks OK.
I test the installer on a 32bit Windows7 system and it works, but on a
64bit Windows7 system it works not. So I think it is a NSIS problem, not
a CPACK problem.
Thanks for the tips.
Ralf
Am Mittwoch, den 25.01.2012, 22:
On 01/21/2012 11:28 AM, Dominik Szczerba wrote:
> On Sat, Jan 21, 2012 at 10:50 AM, Dominik Szczerba
> wrote:
> You might use an EXECUTE_PROCESS() command at the beginning of your
> CMakeLists.txt to unload the modules, and another EXECUTE_PROCESS()
> at the end to reload them.
>>
>>
Hi,
I'm trying to build a very big project with some third party
dependencies, so I want to use ExternalProject capabilities. I'm
deploying on OSX with Xcode.
If I do:
(on the build dir)
$ cmake -D
$ xcodebuild (or open the project with Xcode)
Then build, everything works great.
But, if I refe
2012/1/25 Bill Hoffman :
> On 1/25/2012 9:28 AM, Andrea Crotti wrote:
>>
>> Since I still don't get CMake + NSIS running on Linux, I was trying to
>> build my software
>> on Windows...
>
>
> CMake and NSIS has never been ported to work on Linux, so no surprise there.
In fact there is.
It works for
2012/1/25 Ralf Lange :
> Hello,
> I will prepare a windows installer for my application. The application need
> GStreamer for Windows. The installer has to download the installer and start
> the installer.
> I have add the following command to the CMakeLists.txt file:
>
> SET(CPACK_NSIS_EXTRA_INSTA
On Wednesday 25 January 2012, Phil Smith wrote:
> No, there's no "What version are you?" flag for dasm.
>
> I added
> set(CMAKE_ASM_DIGNUS_COMPILER_ID "DIGNUS")
>
> and now it seems to be invoking regina.exe with just the -o flag. Is that
> the right SET ?
Looks good, are you sure this is
No, there's no "What version are you?" flag for dasm.
I added
set(CMAKE_ASM_DIGNUS_COMPILER_ID "DIGNUS")
and now it seems to be invoking regina.exe with just the -o flag. Is that the
right SET ?
-Original Message-
From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Sent:
On Wednesday 25 January 2012, Brad King wrote:
> On 1/25/2012 1:50 PM, Phil Smith wrote:
> > Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake
> > (in Modules\) is:
> >
> > SET(ASM_DIALECT _DIGNUS)
> > SET(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT "asmit.bat")
> > INCLUDE(CMakeD
On 1/25/2012 1:50 PM, Phil Smith wrote:
Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake (in
Modules\) is:
SET(ASM_DIALECT _DIGNUS)
SET(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT "asmit.bat")
INCLUDE(CMakeDetermineASMCompiler)
SET(ASM_DIALECT)
and that gets invoked several t
Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake (in
Modules\) is:
SET(ASM_DIALECT _DIGNUS)
SET(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT "asmit.bat")
INCLUDE(CMakeDetermineASMCompiler)
SET(ASM_DIALECT)
and that gets invoked several times, with:
dasm.exe --version
dasm.exe -
BTW In my own project, I am using a bit more old-school approach to
document also CMake code. I wrote a Doxygen filter which transforms
the CMake code into C code which Doxygen can generate an HTML
documentation for. The source of this filter implemented in Python can
be found at
http://sourceforg
I am not sure where I found info on this variable, but the ITK/VTK
projects are always a good resource on the latest trends/development
in CMake/CTest/CPack.
Further, for anyone interested, please note the difference in
CTEST_EXTRA_COVERAGE_GLOB, which lists glob expressions as used by
file (GLOB)
I'd like to get an overall update on the plans for this from the kitware
guys, as well as propose an extension to this feature.
Honestly I think the exact facilities we have now for libs we should have
for source directories. This includes:
- debug/release configurations for include directories
-
On Wednesday 25 January 2012, Alfa Omega wrote:
> A little addendum to what I wrote earlier.
>
> On Wed, Jan 25, 2012 at 8:54 AM, Alfa Omega wrote:
> > 2012/1/24 Alexander Neundorf
> >
> >> Hi,
> >>
> >> On Tuesday 24 January 2012, Alfa Omega wrote:
> >> > Hi,
> >> >
> >> > What part does not
On 01/25/2012 02:48 PM, Andrea Crotti wrote:
Now however CMake complains that it can't fin nmake, which from my
search it's something it's this:
http://superuser.com/questions/146577/where-do-i-find-nmake-for-windows-7
so cmake . generated by default the nmake files, but why cpack would
need nma
Hello,
I have tried with the pre-built ones, but those don't detect visual
studio 2005 SP1 correctly on windows 7 64-bit. I had to change the code
to the version below.
I needed to add the "Wow6432Node" in the registry key path. Also, the
VisualStudioProjectsLocation registry key was not there
After emailing directly with Tom, I realized I misinterpreted this
code when I replied to the list
He has the problem with a 64-bit build of CMake itself, I think:
"You built a 64-bit CMake? That might be the explanation. Try building
a 32-bit one instead. Or simply use Kitware's pre-built 32
On 1/25/2012 10:53 AM, Phil Smith wrote:
We've also provided other approaches elsewhere in this thread to
avoid the problem altogether by setting up your toolchain file to
skip compiler id detection.
OK, I'm willing to do that, but I can't figure out how to do so.
Actually the previous discus
>We've also provided other approaches elsewhere in this thread to
>avoid the problem altogether by setting up your toolchain file to
>skip compiler id detection.
OK, I'm willing to do that, but I can't figure out how to do so.
It seems like:
SET(CMAKE_C_COMPILER "regina.exe" "cc.rex dcc.exe"
Hello,
I will prepare a windows installer for my application. The application
need GStreamer for Windows. The installer has to download the installer
and start the installer.
I have add the following command to the CMakeLists.txt file:
SET(CPACK_NSIS_EXTRA_INSTALL_COMMANDS "
NSISdl::download
htt
On 1/25/2012 9:06 AM, Phil Smith wrote:
Just to be clear: that doesn't mean CMake is right -- it's not passing all
> the arguments it should. How to move this forward?
IMO the change to CMake that exposed this was correct. The ARG1
has always been a literal string placed in command shells afte
On 01/25/2012 02:49 PM, Bill Hoffman wrote:
On 1/25/2012 9:28 AM, Andrea Crotti wrote:
Since I still don't get CMake + NSIS running on Linux, I was trying to
build my software
on Windows...
CMake and NSIS has never been ported to work on Linux, so no surprise
there.
Wait, this contradicts t
On 1/25/2012 9:28 AM, Andrea Crotti wrote:
Since I still don't get CMake + NSIS running on Linux, I was trying to
build my software
on Windows...
CMake and NSIS has never been ported to work on Linux, so no surprise there.
I installed CMake and NSIS and all my CMake actually does is to creat
Now however CMake complains that it can't fin nmake, which from my
search it's something it's this:
http://superuser.com/questions/146577/where-do-i-find-nmake-for-windows-7
so cmake . generated by default the nmake files, but why cpack would
need nmake for in the first place if I'm just using NS
On 01/25/2012 02:28 PM, Andrea Crotti wrote:
Since I still don't get CMake + NSIS running on Linux, I was trying to
build my software
on Windows...
I installed CMake and NSIS and all my CMake actually does is to create
an installer:
cmake_minimum_required(VERSION 2.6)
project(try_out)
instal
Since I still don't get CMake + NSIS running on Linux, I was trying to
build my software
on Windows...
I installed CMake and NSIS and all my CMake actually does is to create
an installer:
cmake_minimum_required(VERSION 2.6)
project(try_out)
install(
# is this automatically the source dir??
Just to be clear: that doesn't mean CMake is right -- it's not passing all the
arguments it should. How to move this forward?
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Phil Smith
Sent: Saturday, January 21, 2012 4:50 PM
To: Brad King
C
Thanks, this way works.
Ogre framework is pre-fixed up because it's from Ogre SDK, i.e. should be ready
for redistribution, I think.
On 25.01.2012, at 16:00, David Cole wrote:
>
>
> On Wednesday, January 25, 2012, Nikolay Kasyanov wrote:
> > Already tried, doesn't help.
> > example of output:
On Wednesday, January 25, 2012, Nikolay Kasyanov wrote:
> Already tried, doesn't help.
> example of output:
> warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre' is not
absolute...
> warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre'
A little addendum to what I wrote earlier.
On Wed, Jan 25, 2012 at 8:54 AM, Alfa Omega wrote:
>
> 2012/1/24 Alexander Neundorf
>
>> Hi,
>>
>> On Tuesday 24 January 2012, Alfa Omega wrote:
>> > Hi,
>> >
>> > What part does not follow the convention? I'm using a toolchain file,
>> plus
>> > when I
Already tried, doesn't help.
example of output:
warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre' is not
absolute...
warning: target
'@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre' does not
exist...
/usr/bin/otool: can't open file:
@executa
31 matches
Mail list logo
