Hi,
Is there a way from CMake to provide the build system "path" for a build target?
Sublime Text 2 builds with the defaut system path, which makes the
project build to fail. When the project is built from the shell from
which ST is started there is no issue has the current PATH env. var.
is used
Ooops, sorry for the noise, there was an issue with the CMakeLists.txt file.
Please ignore my last post.
On Wed, Dec 17, 2014 at 10:15 AM, Emmanuel Blot wrote:
> Hi,
>
> Is there a special order to make CMake recognize .S files - with Clang
> toolchain - as valid source files?
>
Hi,
Is there a special order to make CMake recognize .S files - with Clang
toolchain - as valid source files?
-- ASM: /usr/local/bin/clang
-- The ASM compiler identification is Clang
-- Found assembler: /usr/local/bin/clang
-- Configuring done
CMake Error at lib/CMakeLists.txt:9 (ADD_LIBRARY):
Hi,
I need to tweak object files for a target before linking them to the
final executable.
I'm striving for retrieving the file object paths for a target:
ADD_LIBRARY(tgt OBJECT file1.c file2.S)
1. $ is not available from
ADD_CUSTOM_COMMAND/ADD_CUSTOM_TARGET
2. Actual object paths could be ded
Hi,
How to tell CMake to use '.o' output object file (instead of the
Windows' .obj forced alternative) when cross-compiling ?
SET (CMAKE_SYSTEM_NAME Generic)
...
SET (CMAKE_C_OUTPUT_EXTENSION .o)
has no effect from a project file.
forcing SET (UNIX 1) does work, but this is a terrible workaroun
Hi,
I'd like to call genassym from cmake.
>From FreeBSD man page:
sh genassym.sh [-c] C compiler invocation
I do not really get how to perform such a task from CMake, as the "C
compiler invokation" string is similar to what is defined with the
(as retrieved from the
CMAKE_C_COMPILE_OBJECT
ke it to 3.0 release? Could it have been implemented as more of
> a global flag so I don't have to modify every single install() I have?
>
>
> On Thu, May 15, 2014 at 6:07 AM, Emmanuel Blot wrote:
>>
>> > Too bad it did not make it to RC3...
>> > This is
> Too bad it did not make it to RC3...
> This is a really nice feature.
Neither RC4 nor RC5.
Any chance to get it pulled?
Cheers,
Manu
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services t
Succesfully tested, thanks a lot!
Too bad it did not make it to RC3...
This is a really nice feature.
Cheers,
Manu
On Mon, Apr 7, 2014 at 3:07 PM, David Cole wrote:
>> On 6. Apr 2014, at 16:48, David Cole wrote:
>>
>> > The patch says it's based on
>
> "9dadcae57bc8545d1af66ede4c91c06eaa49f9d6
Hi,
Is there a way, in CMake, to change the pattern of the output object
files - that is for each .c compiled, the name of the output binary .o
files.
I'm not refering to the file extension, nor any library name for which
I already found answers in CMake doc, but the basename.
The issue I'm facin
Hi Stefan,
Which cmake base version should be used to apply the patch?
(I tried against 2.8.12.2 and 3.0.0-rc1-1 but I got failure in both cases)
Thanks,
Manu
On Fri, Apr 4, 2014 at 7:17 PM, Stefan Eilemann wrote:
> Hi,
>
> I gave the implementation of install(QUIET) a shot since it became an
Hi,
What is the recommended way to specify compiler flags for Objective-C
source files?
Objective-C is not defined as a specific language in the default CMake
modules (vs. C and C++ for exemple), so CMake does not seem to handle
OBJC flags at all.
How to define OBJCFLAGS for a whole project, in
Hi,
I'm using CMake (2.8.10.1) to cross-compile from OS X and Linux x86_64
hosts to ARM EABI platform running eCos.
I'm looking for a way (and if possible, a clean one ;-)) to define C
compiler flags that are not propagated to the final link stage.
My current CMake files use:
SET (CMAKE_SYSTEM_
> echo -e 'IF (NOT CMAKE_VERSION VERSION_LESS 2.8.4)\nMESSAGE(STATUS
> --no-warn-unused-cli)\nENDIF (NOT CMAKE_VERSION VERSION_LESS 2.8.4)" >>
> cmake_since_2.8.4.cmake
>
> EXTRA_CMAKE_ARGS=$(cmake -P cmake_since_2.8.4 | sed 's/^-- //')
>
> HTH
>
> Eike
Thanks, Eike.
As I already test the CMake v
-- Forwarded message --
From: Emmanuel Blot
Date: Fri, Feb 18, 2011 at 11:48 PM
Subject: Re: [CMake] New warnings in CMake 2.8.4-rc2
To: David Cole
> If a variable is not used, then simply do not define it on the cmake
> command line.
Thanks, but I simply can't. If
> The only warning that is enabled by default is to warn you about
> misspelled -D options that you pass on the command line. (We think
> they *may* be misspelled because they are not referenced in the
> configure/generate steps... So it's just a warning.)
> You can suppress this by also passing "
>> FWIW: I found why I use CMAKE_FORCE_C_COMPILER rather than the simpler
>> CMAKE_C_COMPILER command:
>> I build projects for eCos from outside the eCos tree directory, and
>> CMake has some trouble finding the eCos header files when simply using
>> CMAKE_C_COMPILER. It complains about CMAKE_FIND_
> Currently, there is no way to turn this off.
Very, very bad news ;-(
IMHO, this is a recurrent issue with CMake. It seems there is no way
to guarantee that a project that builds well with a version of CMake
will build the same way with the next minor iteration (used to be
called "patch release")
Hello,
How to disable the new warnings CMake 2.8.4-rc2 emits, such as the
following ones?
CMake Warning: The variable, 'NAMEFUNC', specified manually, was not
used during the generation.
CMake Warning: The variable, 'SAJOBS', specified manually, was not
used during the generation.
CMake Warning:
> Manu,
> please maintain the discussion on the mailing list as these is a general issue
Sure, sorry (actually I replied to your PM, I have not seen it did not
contain a cc: to the ML)
> if you are cross compiling, the target is not cygwin, so CYGWIN is not
> defined.
Ok, understood.
> However
>> INCLUDE (CMakeForceCompiler)
>> CMAKE_FORCE_C_COMPILER (arm-eabi-gcc-4.5.2 GNU 4)
>
> I haven't used that one before.
FWIW: I found why I use CMAKE_FORCE_C_COMPILER rather than the simpler
CMAKE_C_COMPILER command:
I build projects for eCos from outside the eCos tree directory, and
CMake has so
> The docs say that the signature is
> CMAKE_FORCE_C_COMPILER( )
> so maybe something bad happens when you give it that extra
> argument "4"? Try without "4"?
Actually, it changes nothing.
*but* if I remove the specific version number for the compiler, i.e. I define
FIND_PROGRAM (xcc ${XTOOL
Oops, I forgot to post to the ML
-- Forwarded message --
From: Emmanuel Blot
Date: 2011/1/10
Subject: Re: [CMake] Cross-compiling a static library (CMake 2.8.3)
To: Bjørn Forsman
> I haven't used that one before. The docs say it should be used
> when CMake is
> I'm getting the following warning message:
>From http://www.cmake.org/pipermail/cmake/2010-September/039705.html,
it seems on my development environment that _CMAKE_TOOLCHAIN_PREFIX is
left empty.
If I force this variable to the expected value (arm-eabi-), the proper
tools are detected and invo
Hello,
Using the ADD_LIBRARY command for a static library (.a), how to tell
CMake to use the ranlib tool for the target, not the default one for
the host?
I'm getting the following warning message:
cd watchdog && /usr/local/Cellar/cmake/2.8.3/bin/cmake -E
cmake_link_script CMakeFiles/nd_watchdog
Hello All,
I've just bumped into an issue with Cygwin.
I have not compiled with CMake and Cygwin for a while, so I'm not sure
where the problem comes from (Cygwin, CMake, or the combination of
both).
The following command used to work on all platforms (Linux, Mac OS X, Cygwin):
FIND_PROGRAM (x
Hello,
I'm not sure if this issue has already been reported, but ithe
following command:
ENABLE_LANGUAGE (ASM-ATT OPTIONAL)
Triggers the following error, starting at CMake 2.8.3 (worked well up to 2.8.2):
CMake Error at
cmake/Modules/CMakeDetermineASMCompiler.cmake:68
(CMAKE_DETERMINE_COMPILER_
Hi,
I'd like to run some static analysis tool from CTest. (2.8.1)
I've added enable_testing() and add_test() calls in my CMakeLists.txt
file, and the static analysis tool is invoked as expected, however:
* CTest discards both the tool standard output and tool standard
error stream when ran with
> Can you create a bug entry for this?
Sure, I'll do it
> As a quick fix I think if you set CMAKE_OSX_DEPLOYMENT_TARGET to empty it
> will stop CMake form doing this. You should be able to do that either in
> the cache or in your project.
Ok, it seems to work, thanks for the workaround.
Now t
Hi All,
I've just upgraded my CMake installation to 2.8.0, as my collegues
reported me some compilation errors with the new release of CMake
(they use Debian/unstable).
Before I'm able to reproduce the same error they got, I got another
error, on Mac OS X hosts.
It seems that CMake 2.8.0 forces c
But then the second parameter is completely superflous, it just adds
noise and confusion. If you use just add_directory(foo) cmake will
automatically use /foo as builddir for foo.
I don't remember when I've added it, but I *had* to add it at some
point: CMake was not working as expected before
Ideally you wouldn't use linker flags, but just use the target you've
created via add_library. But I guess that doesn't work with the
start-group
stuff. So...
Yeah, at least I've been unable to find a better way to use --start-
group / --end-group
There is no explicit dependencies between
Doing in-source builds is generally considered a bad idea.
Instead do
something like:
ADD_SUBDIRECTORY (${prj} ${prj}/build)
Huh? That snippet above has absolutely nothing to do with in-
source vs.
out-of-source builds. He simply accumulates all his subprojects in a
variable instead of l
Manu, are you actually cutting release snapshots for the customer and
delivering them outside your version control trunk? In that case you
can make -Wno-dev the default by adding
We deliver SDKs, however CMake binaries are not bundled along with our
SDKs.
A SDK that builds w/o a single warn
The installer for CMake 2.6.3 fails to create symbolic links on OS/X
if links already exist (from a previous installation, e.g. CMake 2.6.2
on my machine)
It pops up one error box for each link it fails to create.
Cheers,
Manu
On 23 Feb 2009, at 19:16, Bill Hoffman wrote:
On behalf of myse
Well, sometimes just explaining the problem to somebody already
helps :-)
It does, yes. Thanks again.
The fact is that this library "merging" thing has been existing for a
while. I've changed a directory name and forgot to update the
CMakeListst.txt file accordingly.
The error looked reall
On 15 Oct 2008, at 00:29, Emmanuel Blot wrote:
Please post the code which didn't work for you.
Ooops, sorry, I found the error: there was a typo in the
ADD_LIBRARY(name ...) "name" parameter, which led to an invalid
dependency.
Very sorry for the n
Yes, please.
The one which works and also the one which doesn't.
Ok, I need to recover the old one from SVN.
I guess it is not worth posting it to the ML, should I send you a
private message ?
Thanks,
Emmanuel.
___
CMake mailing list
CMake@cmake.o
Do you actually have to build them as separate static libs or could
you just
build one big static lib ?
No I really can't do otherwise (for various reasons)
Please post the code which didn't work for you.
So basically, the project tree structure is as follow:
sdk/
CMakeLists.txt (A)
Hello,
I don't know how to resolve a dependency issue.
I use CMake to build several static libraries (cross-compilation for
ARM target)
I've added some custom commands to merge the object files of several
libraries (.a files) into a single static library.
However, I don't know how to tell
On 14 Oct 2008, at 01:22, Alexander Neundorf wrote:
Any help would be greatly appreciated,
I'll have a look at it in the next days.
Can you send a small example which fails ?
Don't worry, I think I found the root cause: the trouble seems to come
from the order of the SET() statement i
Hi,
I've just upgrade from CMake 2.6.0 to CMake 2.6.2.
All our C projects that relies on some assembler file (ARM assembly)
are now broken.
I'm not sure about what has changed in CMake so that ASM stopped to
work.
The 3 CMakeASM* files look identical (between 2.6.2 and 2.6.0), we use
"AT
The only way would be something like this:
set(a "-mcpu=arm7tdmi -std=gnu99 -fgnu89-inline -finline-functions")
set(a "${a} -ffunction-sections -fdata-sections ")
set(a "${a} -fno-strict-aliasing -mno-thumb -Os -fomit-frame-pointer")
Ok thanks. Not really handy, but better than nothing ;-)
It
Hi,
Is it possible to write variable definition directives using multiple
lines, i.e.
I have a long definition string such as:
SET (CMAKE_C_FLAGS_RELEASE "-mcpu=arm7tdmi -std=gnu99 -fgnu89-inline -
finline-functions -ffunction-sections -fdata-sections -fno-strict-
aliasing -mno-thumb -Os -s
Until now only the makefile-based generators have been tested for
cross
compiling. XCode probably doesn't work. I have no idea how hard it
would be
to support cross compiling with XCode.
Ok. I've tried to find some information about supporting cross
compilation w/ Xcode, but it's far from
Hi,
Is it possible to use the Xcode generator to produce Xcode projects
for cross-compilation?
It seems that in such a case, CMake ignores the cross-compiler (gcc
4.x), which in turn make Xcode use the native GCC compiler.
Thanks,
Manu
___
CMake
To do that, you could use CheckC[XX]CompilerFlag module and command.
Good point, I have not thought about this option. Thanks.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Are you using GNU as ?
Then the ASM-ATT files should work for you.
I can confirm: ASM-ATT allows to use .s / .S files along with C projects
(GCC for arm-elf within my environment).
BTW, I was wondering how/why the "ATT" version of the ASM module is to
be used ?
I've started using it because t
This is taken from a FindBoost.cmake file I had laying around.
Adjust for your needs:
Thanks, works smoothly.
Manu
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Is there some CMake macro to report the version of the GCC compiler
version?
It seems these macros exist for the CL compiler, but I've not found
the matching macros for GCC.
Some warnings are produced w/ GCC 4, but the matching warning shut-off
option only exists for GCC 4 (not for GCC3).
I
Once you configure in the source tree, CMake will continue to use
the same build tree. So, you need to remove the CMakeCache.txt and
CMakeFiles directory and any configured files from your source tree
and try again.
Ok, thanks a lot.
I thought I had fully cleaned up the source directory, b
I can't figure out why CMake keeps building in the source directory
rather than in the current directory:
$ cmake --version
cmake version 2.6-patch 0
$ echo $PWD
/home/eblot/t380/host/build/project
$ cmake ../../src/project
-- Configuring done
-- Generating done
-- Build files have been writt
In the second project make sure you specify the libraries to link from
the first project by full path. Then the dependencies will be hooked
up. Without a full path CMake does not know how to add a build-time
dependency on a library. You can get a full path in the second
project
by using find
The command
add_custom_command(OUTPUT myout.txt COMMAND ...)
tells CMake how to generate myout.txt. Then you have to tell CMake
you
want to generate it by depending on the output from a target. The
target can either be an executable you're already building:
add_custom_target(MyDriverTarget
Hi,
I'm using CMake to build two C-based projects
The first CMake project builds several static libraries (ARM elf / eCos)
The second CMake project builds several application which do link
against the static libraries produced within the first project.
However, both CMake projects are unrelat
Hi,
I'm using CMake (2.6) to build several C and C++ projects.
I'd like to add another project which would be a pure Python project:
CMake would simply have to invoke Python script (which in turn
generates an output file based on two input files).
What would be the rules to do so ?
I've trie
Hi All,
I'm using CMake to cross-compile projects for eCos on ARM9 targets
(hosts: Windows, Linux & Mac OS X).
Some CMake projects are unit tests (ELF executable files), which need
to be linked against some static libraries (lib.a).
I'd like to add an extra dependency so that the ELF exe fi
This is currently not supported for the MSVC generator.
How about using Eclipse and the CMake Eclipse generator ?
It currently has issues with out-of-source builds, but as long as
you use the
Eclipse generator with in-source builds it should work nicely :-)
Sure, but I really don' t like/don'
Hi all,
Does cmake (2.5 pre) support generation of build files for Visual
Studio (2008 if that matters) projects for cross-compiling to a
different OS/CPU (needs: eCos/ARM).
It seems that when such a generator is selected, CMake simply ignores
the "force compiler" directives and select CL
59 matches
Mail list logo
