On 06.08.08 23:30:44, Alexander Neundorf wrote:
> On Wednesday 06 August 2008, Andreas Pakulat wrote:
> > On 06.08.08 21:16:01, Alexander Neundorf wrote:
> ...
> > > Hmm, what was it...
> > > Asking whether it should add all files in the subdirs to the project
> > > maybe.
> >
> > Uhm, that sounds
On 8/6/08, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> Mike Jackson wrote:
>> I have the following:
>>
>> SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
>> #DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
>> #RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
>> FRAMEWORK TRUE
>>
Is 'failed' for " Detecting C compiler ABI info" OK (it seems to work, just
paranoid at this point)?
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- Check for working C compiler: c:/progra~1/dignus/cc.bat
-- Check for working C compiler: c:/progra~1/di
C:\temp>cmake -P CMakeLists.txt
-- x length: 2
-- y length: 1
C:\temp>
I get the same result in "my" directory (with the file renamed, of course).
Ah HAH -- if I comment out:
# INCLUDE (CMakeForceCompiler)
# CMAKE_FORCE_C_COMPILER (c:/progra~1/dignus/cc.bat Dignus)
# CMAKE_FORCE_CXX_COMPILER (
On Aug 6, 2008, at 6:52 PM, Bill Hoffman wrote:
Mike Jackson wrote:
I have the following:
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
#DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
#RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
FRAMEWORK TRUE
FRAMEWORK_VERSION $
Thankyou very much for this.
Andrew
On Thu, Aug 7, 2008 at 5:13 AM, Brad King <[EMAIL PROTECTED]> wrote:
> Andrew Maclean wrote:
>> Putting it succintly, I want to glob all files in some directory not
>> part of the cmake source or binary directories and create a variable
>> containing these fil
Mike Jackson wrote:
I have the following:
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
#DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
#RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
FRAMEWORK TRUE
FRAMEWORK_VERSION ${MXADATAMODEL_VER}
RESOURCE ""
DEBUG_P
Hi Alex
2008/8/7 Alexander Neundorf <[EMAIL PROTECTED]>:
> On Wednesday 06 August 2008, ning wrote:
>> Hi, Alex
>>
> ...
>> I removed force compiler inclusion from CMAKE_TOOLCHAIN_FILE and
>> "if (CMAKE_CROSSCOMPILING)" clause from CMakeLists.txt to try
>> set(CMAKE_C_COMPILER
>> "arm-wrs-
On Jul 31, 2008, at 8:12 AM, Stephan Diederich wrote:
Hi,
I just found an issue while moc'ing one of our headers.
We have some #ifndeffed slots in that header which depend on -DWIN32.
A default qmake ".pro" project adds
-D_MSC_VER=1400 -DWIN32
on windows, MSVC8. The QT4_WRAP_CPP does not defi
On Wednesday 06 August 2008, Phil Smith wrote:
> Harrumph:
>
> C:\temp>cmake -G"Unix Makefiles" .
> -- The C compiler identification is unknown
> -- The CXX compiler identification is unknown
> -- Check for working C compiler: CMAKE_C_COMPILER-NOTFOUND
> CMake Error: your C compiler: "CMAKE_C_COMPI
2008-08-06 21:05:50 Brad King napisał(a):
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2008-08-06 14:06:47 Bill Hoffman napisał(a):
> >> Arfrever Frehtes Taifersar Arahesis wrote:
> >>
> Can you do a find in your build tree and find CMakeError.log?
> >>> `find -name CMakeError.log` doesn't
Harrumph:
C:\temp>cmake -G"Unix Makefiles" .
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- Check for working C compiler: CMAKE_C_COMPILER-NOTFOUND
CMake Error: your C compiler: "CMAKE_C_COMPILER-NOTFOUND" was not found.
Please set CMAKE_C_COMPILER
I have the following:
SET_TARGET_PROPERTIES(${MXADATAMODEL_LIB_NAME} PROPERTIES
#DEBUG_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
#RELEASE_OUTPUT_NAME ${MXA_LIBRARY_RELEASE}
FRAMEWORK TRUE
FRAMEWORK_VERSION ${MXADATAMODEL_VER}
RESOURCE ""
DEBUG_POSTFIX _debug
)
an
On Wednesday 06 August 2008, Phil Smith wrote:
> I added the last line in the following block in
> CMakeDetermineCCompiler.cmake (insertion after line 69):
>
> LIST(LENGTH CMAKE_C_COMPILER _CMAKE_C_COMPILER_LIST_LENGTH)
> IF("${_CMAKE_C_COMPILER_LIST_LENGTH}" EQUAL 2)
> LIST(GET CMAKE_C_COM
I added the last line in the following block in CMakeDetermineCCompiler.cmake
(insertion after line 69):
LIST(LENGTH CMAKE_C_COMPILER _CMAKE_C_COMPILER_LIST_LENGTH)
IF("${_CMAKE_C_COMPILER_LIST_LENGTH}" EQUAL 2)
LIST(GET CMAKE_C_COMPILER 1 CMAKE_C_COMPILER_ARG1)
LIST(GET CMAKE_C_COMPI
On Wednesday 06 August 2008, Andreas Pakulat wrote:
> On 06.08.08 21:16:01, Alexander Neundorf wrote:
...
> > Hmm, what was it...
> > Asking whether it should add all files in the subdirs to the project
> > maybe.
>
> Uhm, that sounds strange, kdevelop never asks that for files that are
> already i
My Bad.. I had what seems to be conflicting commands for doing this..
So. Just to be clear the below _does_ work just fine.
Sorry for the noise.
--
Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On Aug 6, 2008, at 4:46 PM, David Cole wrote:
set_property(
On Wednesday 06 August 2008, ning wrote:
> Hi, Alex
>
...
> I removed force compiler inclusion from CMAKE_TOOLCHAIN_FILE and
> "if (CMAKE_CROSSCOMPILING)" clause from CMakeLists.txt to try
> set(CMAKE_C_COMPILER
> "arm-wrs-linux-gnueabi-gcc"
> "--sysroot=${SYSROOT_PATH} -mfloat-abi=
set(deepPublicHeaders fooDeepPublic.h fooDeepPublic1.h fooDeepPublic2.h
..)
set_property(SOURCE ${deepPublicHeaders}
PROPERTY MACOSX_PACKAGE_LOCATION Headers/Deep
)
...should work, too. One call per list of headers with a unique folder name
shouldn't be *too* verbose.
On Wed, Aug 6, 20
On Wed, Aug 6, 2008 at 1:55 PM, Yuri V. Timenkov
<[EMAIL PROTECTED]> wrote:
> On Wednesday 06 August 2008 17:43:18 Yann Cointepas wrote:
>> Hi,
>>
>> Is there a way to define component group (or installation type)
>> specific installation targets in a Makefile ?
>>
>> I work on Linux. I have define
I am starting to explore the Framework creation from CMake 2.6. In my
first attempt things generally were created correctly except for the
Headers folder. All my includes are in a flat hierarchy. I need my
Headers to retain their folder layout like they do when creating a
normal dylib insta
Hi Frans,
On Wednesday 06 August 2008, [EMAIL PROTECTED] wrote:
> Hello again,
>
> after Bill corrected my awkward make/nmake confusion, at least compiling
> works now for me under the following circumstances:
>
> * build for the phone (in contrast to the emulator)
> * S60 3rd FP1 (9.2) SDK with g
On Wednesday 06 August 2008, Phil Smith wrote:
> No errors, no CMakeError.log -- just null values for the SIZEOF_LONG_LONG
> et al.
>
> It sets CMAKE_C_COMPILER_ARG1 in CMakeDetermineCCompiler.cmake -- but
> inside: IF(NOT CMAKE_C_COMPILER)
>
> ...so it doesn't do it if you explicitly specify a C c
On 06.08.08 21:16:01, Alexander Neundorf wrote:
> On Wednesday 06 August 2008, Andreas Pakulat wrote:
> > On 06.08.08 20:29:07, Yogesh Marwaha wrote:
> > > 2008/8/6 Andreas Pakulat <[EMAIL PROTECTED]>:
> > > > It would be interesting to see how the file initially looked. KDevelop
> > > > automatica
On Wednesday 06 August 2008, Phil Smith wrote:
> OK, once I get it working for real, I'll do this.
:-)
> But I think I confused you. ZOS is the OS (really z/OS). System z is the
> hardware platform. Dignus is the compiler.
>
> So shouldn't the files be named Systemz-Dignus-C.cmake etc.?
No, it's
ok, thanks for the report... I'll check in a solution later.
--Miguel
On Wed, Aug 6, 2008 at 3:55 PM, Steven Van Ingelgem
<[EMAIL PROTECTED]> wrote:
> Yeah, I did that and that worked ;-)
>
> 2008/8/6 Miguel A. Figueroa-Villanueva <[EMAIL PROTECTED]>
>>
>> Change the line to the following and let
Yeah, I did that and that worked ;-)
2008/8/6 Miguel A. Figueroa-Villanueva <[EMAIL PROTECTED]>
> Change the line to the following and let me know if it works:
>
> NAMES msw/build.cfg mswd/build.cfg mswu/build.cfg mswud/build.cfg
>
___
CMake mailing lis
Change the line to the following and let me know if it works:
NAMES msw/build.cfg mswd/build.cfg mswu/build.cfg mswud/build.cfg
--Miguel
On Wed, Aug 6, 2008 at 2:30 PM, Steven Van Ingelgem
<[EMAIL PROTECTED]> wrote:
> around line 452 & 461 there is being searched for the library directory...
> B
On Wednesday 06 August 2008, Olaf Peter wrote:
> Hi,
>
> the following command line works as expected (out of source build):
>
> $ ../cmake-2.6.1-Linux-i386/bin/cmake ../project
> -- The C compiler identification is GNU
> ...
> -- Configuring done
> -- Generating done
> -- Build files have been wri
Andrew Maclean wrote:
> Putting it succintly, I want to glob all files in some directory not
> part of the cmake source or binary directories and create a variable
> containing these files to be copied to the binary build location.
> file(GLOB ... ) only seems to work on the current directory.
The
On Wednesday 06 August 2008, Andreas Pakulat wrote:
> On 06.08.08 20:29:07, Yogesh Marwaha wrote:
> > 2008/8/6 Andreas Pakulat <[EMAIL PROTECTED]>:
> > > It would be interesting to see how the file initially looked. KDevelop
> > > automatically removes any entries which point to non-existing files
Arfrever Frehtes Taifersar Arahesis wrote:
> 2008-08-06 14:06:47 Bill Hoffman napisał(a):
>> Arfrever Frehtes Taifersar Arahesis wrote:
>>
Can you do a find in your build tree and find CMakeError.log?
>>> `find -name CMakeError.log` doesn't return anything.
>>>
>> Can you do this:
>>
>> cmake
On 06.08.08 20:29:07, Yogesh Marwaha wrote:
> 2008/8/6 Andreas Pakulat <[EMAIL PROTECTED]>:
> > It would be interesting to see how the file initially looked. KDevelop
> > automatically removes any entries which point to non-existing files and
> > I guess the cmake generator has wrong assumptions ab
Hello,
I'm using CMake 2.6 and MS Visual Studio 2005.
I need to set different compile flags to my source files depending on
the configuration (debug or release).
I've checked the mailing list and I found a thread talking about it
(http://www.cmake.org/pipermail/cmake/2006-December/012148.htm
On Wednesday 06 August 2008, Yann Cointepas wrote:
> Hi,
>
> Is there a way to define component group (or installation type)
> specific installation targets in a Makefile ?
>
> I work on Linux. I have defined three CPack component groups (and/or
> installation types) for my project: runtime, devel
[EMAIL PROTECTED] wrote:
> Here is a directory layout example which produces errors for me (actual names
> replaced for confidence reasons)
Thanks for the simplified example and analysis of character counts.
> C:\a\bb\CMake_Environment\c\CMakeLists.txt
>
> mentio
around line 452 & 461 there is being searched for the library directory...
But... What if you compile like me only a unicode version? Then the
following will never be found:
NAMES msw/build.cfg mswd/build.cfg
Greetings,
Steven
___
CMake mailing
On Wednesday 06 August 2008 17:43:18 Yann Cointepas wrote:
> Hi,
>
> Is there a way to define component group (or installation type)
> specific installation targets in a Makefile ?
>
> I work on Linux. I have defined three CPack component groups (and/or
> installation types) for my project: runtime
On Wednesday 06 August 2008 21:04:30 Olaf Peter wrote:
> Hi,
>
> the following command line works as expected (out of source build):
>
> $ ../cmake-2.6.1-Linux-i386/bin/cmake ../project
> -- The C compiler identification is GNU
> ...
> -- Configuring done
> -- Generating done
> -- Build files have
Hi,
the following command line works as expected (out of source build):
$ ../cmake-2.6.1-Linux-i386/bin/cmake ../project
-- The C compiler identification is GNU
...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/olaf/build
but:
$ ../cmake-2.6.1-Linux-i386/bin/
On 2008-08-06 16:19+0200 Hendrik Sattler wrote:
Zitat von Alberto Luaces <[EMAIL PROTECTED]>:
El Lunes 04 Agosto 2008ES 19:06:07 Hendrik Sattler escribi�:
Cmake-2.6 is not going to be in Debian Lenny, so no real time pressure
on
this.
cmake 2.6 is already on lenny, see it at
Hmm, bad timi
2008-08-06 14:06:47 Bill Hoffman napisał(a):
> Arfrever Frehtes Taifersar Arahesis wrote:
>
> >>>
> >> Can you do a find in your build tree and find CMakeError.log?
> >
> > `find -name CMakeError.log` doesn't return anything.
> >
> Can you do this:
>
> cmake --debug-trycompile
>
> Then tar up
Hi!
Does CTest have any support for acyclic unit/regression/functionality
test dependencies? i.e. can you enforce that certain tests pass before
continuing with the others? Also, is there any support for
automatically figuring out what these dependencies are based on source
code #includes etc.?
Che
Hi Brad,
hm, it does'nt seem to be the maximum file name length alone. Many files which
have only the full pathname length in common (about 250) throw an error.
But files with some more characters don't produce errors.
For me it looks like something like a string resize problem in nmake :)
Here
2008/8/6 Andreas Pakulat <[EMAIL PROTECTED]>:
> It would be interesting to see how the file initially looked. KDevelop
> automatically removes any entries which point to non-existing files and
> I guess the cmake generator has wrong assumptions about what it can put
> into the filelist.
>
Here is t
And again..
I moved an ADD_DEFINITIONS instruction to my symbian toolchain file:
ADD_DEFINITIONS(-include
"\"C:/Symbian/9.2/S60_3rd_FP1/EPOC32/INCLUDE/GCCE/GCCE.h\"" )
now the include flag is added twice to the compiler command even after deleting
every intermediately generated cache file m
Zitat von Alberto Luaces <[EMAIL PROTECTED]>:
El Lunes 04 Agosto 2008ES 19:06:07 Hendrik Sattler escribió:
Cmake-2.6 is not going to be in Debian Lenny, so no real time pressure on
this.
cmake 2.6 is already on lenny, see it at
Hmm, bad timing then. They must have requested an exception to t
OK, once I get it working for real, I'll do this.
But I think I confused you. ZOS is the OS (really z/OS). System z is the
hardware platform. Dignus is the compiler.
So shouldn't the files be named Systemz-Dignus-C.cmake etc.?
...phsiii
-Original Message-
From: Alexander Neundorf [mailt
No errors, no CMakeError.log -- just null values for the SIZEOF_LONG_LONG et al.
It sets CMAKE_C_COMPILER_ARG1 in CMakeDetermineCCompiler.cmake -- but inside:
IF(NOT CMAKE_C_COMPILER)
...so it doesn't do it if you explicitly specify a C compiler, a la:
SET(CMAKE_C_COMPILER "c:/p
Hi,
Is there a way to define component group (or installation type)
specific installation targets in a Makefile ?
I work on Linux. I have defined three CPack component groups (and/or
installation types) for my project: runtime, devel and doc and I would
like to be able to install all components o
[EMAIL PROTECTED] wrote:
> might there be a maximum path length limitation in CMake (or perhaps in
> nmake)? Trying to compile a library I have to comment out every source
> file that leads to a CMakeFiles/... object file with a total path length
> of over 200.
>
> Is that a known problem and can
Arfrever Frehtes Taifersar Arahesis wrote:
Can you do a find in your build tree and find CMakeError.log?
`find -name CMakeError.log` doesn't return anything.
Can you do this:
cmake --debug-trycompile
Then tar up and zip the whole thing and email it to me off the list.
Thanks.
--
Bill H
Hi again,
might there be a maximum path length limitation in CMake (or perhaps in nmake)?
Trying to compile a library I have to comment out every source file that leads
to a CMakeFiles/... object file with a total path length of over 200.
Is that a known problem and can I avoid it despite by
Hello again,
after Bill corrected my awkward make/nmake confusion, at least compiling works
now for me under the following circumstances:
* build for the phone (in contrast to the emulator)
* S60 3rd FP1 (9.2) SDK with gcce
* CMake 2.6.1
* OpenC with P.I.P.S. installed
again, for those who w
Hi,
El Lunes 04 Agosto 2008ES 19:06:07 Hendrik Sattler escribió:
> Cmake-2.6 is not going to be in Debian Lenny, so no real time pressure on
> this.
cmake 2.6 is already on lenny, see it at
http://packages.debian.org/lenny/cmake
___
CMake mailing list
On 06.08.08 11:47:20, Yogesh Marwaha wrote:
> Project files are not listed in "File Groups" section of KDevelop
> (3.5.2) when project file is generated through "cmake -GKDevelop3"
> I generate kdevelop project files via cmake 2.6.1 kdevelop3 generator.
> When I open the project, no file of my proj
56 matches
Mail list logo