-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Pakulat schrieb:
> On 26.10.09 12:27:24, Bill Hoffman wrote:
>> Andreas Pakulat wrote:
>>> But that should be the case if I start kdevelop from a cmd.exe that had
>>> vcvars32.bat called. However it seems that executing cmake still fails when
>
On Win64, in a 32-bit calling environment, there are two environment
variables with values like this:
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_ARCHITEW6432=AMD64
In a pure 64-bit calling environment, there is just:
PROCESSOR_ARCHITECTURE=AMD64
(and no value for PROCESSOR_ARCHITEW6432)
...so: you coul
All the WIN32 flags say they are valid for WIN64 machines. Is there no
equivalent WIN64 flag to determine if the OS is 32 or 64 bit regardless of
the bitness of the build?
Thanks,
James
___
Powered by www.kitware.com
Visit other Kitware open-source pro
Is it possible to set up custom commands with add_custom_command so that the
behavior is configuration dependent? Ie, the command does it's thing one
way in Release configuration, but another in Debug configuration.
What I really have is a custom command that is used to turn source files in
one
On Mon, 2009-10-26 at 17:14 -0400, David Cole wrote:
> Where does GLOM_LDFAGS get set?
I believe, from
pkg_search_module(GLOM glom-1.12>=1.12.0)
The whole thing is here:
http://github.com/murraycu/qlom/blob/qlom_cmake/CMakeLists.txt
But really, the point is that I don't know what I should be
Where does GLOM_LDFAGS get set?
Seems like it should end up as space separated itself, rather than being a
cmake list. (If it were space separated then it would work with or without
quotes...) You'll probably want it with quotes though in case there are any
embedded semi-colons.
On Mon, Oct 26,
On Mon, 2009-10-26 at 16:22 -0400, David Cole wrote:
> Try:
> set_target_properties(qlom
>PROPERTIES
>LINK_FLAGS ${GLOM_LDFLAGS})
>
>
> (without the double quotes).
Sorry, the quotes were a random attempt to fix this error, which comes
back when I remove the quotes:
set_tar
Try:
set_target_properties(qlom
PROPERTIES
LINK_FLAGS ${GLOM_LDFLAGS})
(without the double quotes).
On Mon, Oct 26, 2009 at 2:46 PM, Murray Cumming wrote:
> On Fri, 2009-10-23 at 13:42 +0200, Murray Cumming wrote:
> > pkg_search_module() defines SOMEPREFIX_LIBRARY_DIRS among
On Fri, 2009-10-23 at 13:42 +0200, Murray Cumming wrote:
> pkg_search_module() defines SOMEPREFIX_LIBRARY_DIRS among other things,
> as mentioned here
> http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindPkgConfig.cmake?root=CMake&view=markup
> (better than the documentation at
> http://www
in 2.8.0, FindwxWidgets.cmake strips -D from wxWidgets_DEFINITIONS. Why?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane or...@cora.nwra.com
Boulder, CO 80301 http:
On Monday 26 October 2009, Dixon, Shane wrote:
> Is adding the kdevelop generator for Windows on the roadmap now that the
> KDE project has a Windows installer? Looks like Kdevelop is still
> considered unstable, but does install. Any plans on when we can generate
> working Kdevelop environments
On 26.10.09 11:36:10, Dixon, Shane wrote:
> Is adding the kdevelop generator for Windows on the roadmap now that the
> KDE project has a Windows installer?
If you look closely its the KDevelop3 generator and the "3" in there is on
purpose. KDevelop4 (the only version that might eventually run on w
I never really pursued it. I don't know if packaging UseLATEX.cmake with CMake
is the right thing to do, but if that's what users want and the CMake
developers agree, I have no problem with putting it there.
-Ken
On 10/26/09 11:40 AM, "James C. Sutherland" wrote:
On Oct 26, 2009, at 8:13
On Oct 26, 2009, at 8:13 AM, Moreland, Kenneth wrote:
Consider using the UseLATEX.cmake collection of macros. It supports
out-of-source builds (in fact, sort of enforces them) and handles
copying .sty files as well as all sorts of other sticky little
issues with building LaTeX files. You
Is adding the kdevelop generator for Windows on the roadmap now that the KDE
project has a Windows installer? Looks like Kdevelop is still considered
unstable, but does install. Any plans on when we can generate working Kdevelop
environments in Windows?
--
Shane Dixon
Linux Engineer
Atmel Co
Hendrik Sattler wrote:
Zitat von Giampiero Salvi :
I have a project that builds fine both on Linux and on mingw32 using
cmake version 2.6-patch 2.
Now, I am trying to cross compile my project on a Linux (Ubuntu 9.04)
machine for the target Windows platform using the mingw32 cross
compiler. I ha
On 26.10.09 12:27:24, Bill Hoffman wrote:
> Andreas Pakulat wrote:
>> But that should be the case if I start kdevelop from a cmd.exe that had
>> vcvars32.bat called. However it seems that executing cmake still fails when
>> spawned via win32 process api. I'll get back when I have more data about
>>
Andreas Pakulat wrote:
On 26.10.09 11:21:07, Bill Hoffman wrote:
Andreas Pakulat wrote:
Hi,
in kdevelop4 we're running cmake to prepare a builddirectory from a source
dir. This worked just fine on linux, however we're running into a problem
when executing on Windows for the NMake-Generator.
I
That solution works pretty good Mike. Not quite what I thought I was
looking for, but it works.
-
Aaron Wright
Software Engineer - DCS Group
Schweitzer Engineering Laboratories, Inc.
Pullman, WA 99163
509-334-8087
Mike Jackson
Sent by: c
On 26.10.09 11:21:07, Bill Hoffman wrote:
> Andreas Pakulat wrote:
>> Hi,
>>
>> in kdevelop4 we're running cmake to prepare a builddirectory from a source
>> dir. This worked just fine on linux, however we're running into a problem
>> when executing on Windows for the NMake-Generator.
>>
>> It seem
Andreas Pakulat wrote:
Hi,
in kdevelop4 we're running cmake to prepare a builddirectory from a source
dir. This worked just fine on linux, however we're running into a problem
when executing on Windows for the NMake-Generator.
It seems this generator absolutely needs a shell (i.e. cmd.exe) as i
Hi,
in kdevelop4 we're running cmake to prepare a builddirectory from a source
dir. This worked just fine on linux, however we're running into a problem
when executing on Windows for the NMake-Generator.
It seems this generator absolutely needs a shell (i.e. cmd.exe) as its
environment and its no
Zitat von Giampiero Salvi :
I have a project that builds fine both on Linux and on mingw32 using
cmake version 2.6-patch 2.
Now, I am trying to cross compile my project on a Linux (Ubuntu 9.04)
machine for the target Windows platform using the mingw32 cross
compiler. I have a toolchain more or l
Hi,
I have a project that builds fine both on Linux and on mingw32 using
cmake version 2.6-patch 2.
Now, I am trying to cross compile my project on a Linux (Ubuntu 9.04)
machine for the target Windows platform using the mingw32 cross
compiler. I have a toolchain more or less copied from
http
Consider using the UseLATEX.cmake collection of macros. It supports
out-of-source builds (in fact, sort of enforces them) and handles copying .sty
files as well as all sorts of other sticky little issues with building LaTeX
files. You can the macros and the documentation for them on this Wiki
Hi All,
I'm trying to add a rules to my latex build (included in a bigger
project) so that a .sty file is copied in the current_binary_dir.
I've tried several things but can't get the .sty file copied in the
build directory, latex complain about it when i try "make".
Any help would be apprec
Recently, someone ask for PKG_SEARCH_MODULE
At first, I thought simple flag is flag:
PROJECT(MiG)
INCLUDE (FindPkgConfig)
# For GTK
PKG_SEARCH_MODULE(GTK REQUIRED gtk+-2.0)
SET(_targetname ULS)
SET(_src CTest.c)
ADD_EXECUTABLE(${_targetname} ${_src})
SET_TARGET_PROPERTIES(${_targetname}
27 matches
Mail list logo
