On Wed, Oct 28, 2015 at 6:43 AM, Robert Dailey wrote:
> I'm using CMake + Ninja against GCC 4.9 in the Android NDK. I'm on
> Windows, invoking 'ninja' through CMD.exe.
>
> I do not see colored output for diagnostics (errors, warnings, etc)
> GCC gives. Is there something in CMake I need to configu
Something like
CMAKE_MINIMUM_REQUIRED(VERSION 3.1)
SET(CMAKE_CXX_STANDARD 11)
I think.
On Wed, Oct 21, 2015 at 12:43 PM, Chris Stankevitz
wrote:
> Hi,
>
> Q: What is the "CMake way" to ask that the compiler be setup for c++11?
>
> FYI I could not find the answer at
> https://cmake.org/cmake/hel
page contains information on how to fix the
> paths in the config file to be relative instead of absolute. That should fix
> the problem:
>
> https://cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file
>
>
>
> On Mon, Oct 19, 2015 at 11:15 PM, Dan Kegel
Well, that's one answer. But if you want to use system libpcap, it's not a
very satisfying one.
It's odd that pcap doesn't ship with a .pc file.
I guess the pcap folks are hostile to pkgconfig because it's LGPL; see
https://github.com/the-tcpdump-group/libpcap/issues/374
- Dan
On Mon, Oct 19,
On Mon, Oct 12, 2015 at 8:22 PM, Matthew S Wallace
wrote:
> Consider the following CMakeLists.txt (hello.cpp is some standard hello world
> program)
>
> cmake_minimum_required (VERSION 2.6)
> project(HelloWorld)
> add_executable(hello hello.cpp)
> set(WARNING_FLAGS -Wno-char-subscripts -Wno-unuse
IMHO it's a bug to have different contents in the two archive formats; it
leads to confusion like this because it differs from standard practice in
the open source world.
On Oct 1, 2015 7:45 PM, "David Cole via CMake" wrote:
> The "-1" bz2 files are for Cygwin...
>
> Try the plain old .tar.gz ins
"John Barbero Unenge" wrote:
>
> I'm tearing my hair out about how to include thrid party libraries in my
cmake project. Currently I build Poco and a bunch of others that all
generate their respective Config.cmake which I use with
find_package. I have a wrapping build script that builds all of my
On Sep 12, 2015 4:54 PM, "Seth Cantrell" wrote:
>
> I would prefer to not be required to use the .app bundle directory
structure at all. I'm not producing a .app. The program is a command line
program intended to be run directly from Terminal.app, not a GUI program
intended to be launched from Mac
On Sat, Sep 12, 2015 at 1:52 PM, Seth Cantrell wrote:
> I have a project which uses fixup_bundle on Windows to package up the exe
> with the third-party dlls it requires. On Mac OS X this same packaging
> process fails. It looks like on Mac OS X this utility is assuming I want to
> producing a
args to the function, so
> it looks like you got "unlucky" with the number of paths in the prop value.
> I would advise against playing roulette for a while... ;-)
>
> https://github.com/Kitware/CMake/blob/422d3f68/Source/cmSetTargetPropertiesCommand.cxx#L36-L40
>
>
> HT
Thanks. Should set_target_properties throw an error if given too many
arguments, to catch this problem?
Am 10.08.2015 11:43 nachm. schrieb "Nils Gladitz" :
> On 08/11/2015 12:51 AM, Dan Kegel wrote:
>
>> With cmake 2.8.12.2,
>>
>> SET_TARGET_PROPER
With cmake 2.8.12.2,
SET_TARGET_PROPERTIES (foo PROPERTIES INSTALL_RPATH ${my_install_rpath})
silently only obeys the first directory in the rpath, but
SET_TARGET_PROPERTIES (foo PROPERTIES INSTALL_RPATH "${my_install_rpath}")
works. Is it still that way in the latest cmake, and is there
alre
I've been using cygwin buildbot for some time, doing pure windows
builds. The trick is to have the cygwin buildslave unset a few environment
variables (like cygwin's PATH and TEMP and temp), then run a windows
batch file to do everything involving compilers, e.g. running
windows cmake. There is a
f you
run into trouble.
- Dan
On Wed, Aug 5, 2015 at 4:27 PM, Owen Alanzo Hogarth wrote:
> do you have any example of that?
>
> Would it be a custom command? I haven't seen anything like this being done
> before?
>
> On Thu, Aug 6, 2015 at 5:08 AM, Dan Kegel wrote:
>&
On Wed, Aug 5, 2015 at 3:17 PM, Owen Alanzo Hogarth wrote:
> I can put those in some type of array in my c source code. Now is it
> possible to send that list back to cmake at build time so that it can copy
> those files to the binary tree on each build?
You can write a script that parses the C s
On Fri, Jul 31, 2015 at 11:44 AM, Daniel Schepler
wrote:
>> Here's another example from real life. Maybe I'm just being an idiot,
>> but this is what I had to do to set a default:
>>
>> IF(DEFINED CMAKE_BUILD_TYPE AND (NOT ${CMAKE_BUILD_TYPE} STREQUAL "None"))
>>SET(CMAKE_BUILD_TYPE ${CMAKE_B
On Fri, Jul 31, 2015 at 11:43 AM, Bill Hoffman wrote:
> Something like:
> $CACHE{A}
>
> Then, it would never be confused with the the variable A. However, getting
> rid of the cache would not be something that could be done.
Having a cache for invariants is a good thing if it could be done witho
On Fri, Jul 31, 2015 at 11:33 AM, Ruslan Baratov
wrote:
>>> I never use the GUI, and consider the cache an anti-feature there solely
>>> to support GUI users. It complicates my life, and I'd love to see it go.
>>
>> In what way do you think it is causing you trouble?
>
> Here is an example:
>
>
On Fri, Jul 31, 2015 at 2:05 AM, Nagy-Egri Máté Ferenc wrote:
> I agree that JSON looks better. I have no fetish about XML and I could be
> convinced on just about anything in the choice of the IR. The only important
> point is that it SHOULD EXIST and be well defined. Hooking all the
> generators
Am 30.07.2015 10:15 vorm. schrieb "Bill Hoffman" :
>
> On 7/30/2015 10:48 AM, Dan Kegel wrote:
>>
>> I wouldn't mind getting rid of the cache, it's a bizarre concept that
appears
>> to be a workaround for users who can't stand starting cmake from
On Thu, Jul 30, 2015 at 9:30 AM, David Cole wrote:
> json is SOOO much sexier than XML. ;-)
shiny, shiny json :-)
Agreed, json is not covered with ugly-stink. I like it and use it daily.
I'm not at all sure that stateless build languages are a win in the
multiplatform general case.
They p
>> The big selling point would be the ability to introduce arbitrary
>> front-ends to CMake, not just CMakelists.txt. Every developer could
>> choose an input language that suits their project/needs/skills.
>
> I don't like that idea.
>
> Many different languages would make supporting (
A user was confused just now by cmake continuing to output lots and
lots of stuff after
an error. How can we convince cmake to stop immediately upon first error?
The error in this case was
CMake Error at CMakeLists.txt:690 (add_executable):
add_executable cannot create target "ImageClotTest" b
It can't installiert both foo.h and Foo.h in the mac, better correct your
example.
Am 21.07.2015 5:19 vorm. schrieb "Steven Wilson" <
steven.wesley.wil...@gmail.com>:
> I've noticed that CMake 3.3.0-rc3 will not install a header file in a Mac
> OS X framework if the header file starts with a capi
So maybe the yasm source needs to have a keyword or two
added to select PIC addressing mode?
Random googling finds suggestions at
http://cvs.tortall.net/pipermail/bug-yasm/2011-October/86.html
On Wed, Jul 8, 2015 at 10:11 AM, Steve Borho wrote:
> On 07/07, Dan Kegel wrote:
>> On T
On Tue, Jul 7, 2015 at 2:25 PM, Steve Borho wrote:
> We're already adding -fPIC to the compile flags for the two object
> libraries. This way one set of objects can be used to output the shared
> library and the static library. So the C++ files are already compiled
> with -fPIC. It is only a probl
On Tue, Jul 7, 2015 at 12:36 PM, Steve Borho wrote:
> /bin/ld: common/CMakeFiles/common.dir/x86/pixel-a.asm.o: relocation
> R_X86_64_PC32 against symbol `x265_pw_1' can not be used when making a
> shared object; recompile with -fPIC
> ...
> 2 - is there some invocation that will force cmake to bui
I was using add_custom_command to execute three commands, triggering
that rule with add_custom_target, and it worked great with make and
ninja on linux and mac.
Over on Windows, though, with visual c++ 2013 and cmake 3.0.1, only
the first of the three commands was executed.
After much head-scratch
Did you try the workaround suggested in the first link you gave, i.e.
set( RatherLongLibraryName_GUID_CMAKE CACHE INTERNAL
"remove this and Visual Studio will mess up incremental builds")
On Sun, May 31, 2015 at 9:04 AM, wrote:
> Unfortunately, we're hitting an issue migrating from VS 2012 to
Write a wrapper script that sets the variables and invokes the compiler,
and tell cmake that's your compiler.
--
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 to support the CMake communi
On Mon, May 4, 2015 at 12:07 PM, Martin Percossi wrote:
> Could someone point me to a recent example CMakeLists.txt for creation of an
> application (i.e., .app directory structure) under OSX? Ideally, it should
> have its own custom framework included in the @executable_path/../Frameworks
> direc
If "sudo make install" is done in btmp, it leaves a file called
"install_manifest.txt" in the btmp directory owned by root. This causes a later
non-sudo "make install" (where configuration has changed the destination
directory to something that does not require sudo) to fail.
Perhaps "make install
Is "Mastering CMake" still the only book out there?
BTW, the doc site for 3.0 is great, I really appreciate the effort
that went into it.
- Dan
--
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 se
I'm facing the question of static myself now, porting a large automake
project to cmake.
I guess I'll mirror automake's practice of having separate
--enable-static and --enable-shared settings, and allow both to be
built at once.
It's a bit ambiguous (which one gets tested?), but since I'm just
r
install()
> command in any way, it's just how CMake works.
>
> Petr
>
> On Thu, Oct 16, 2014 at 4:13 AM, Dan Kegel wrote:
>
>> > This turned out to work for me:
>> >
>> > install (
>> > DIRECTORY ${samples_SOURCE_DIR}
>
> This turned out to work for me:
>
> install (
> DIRECTORY ${samples_SOURCE_DIR}
> DESTINATION "src"
> PATTERN "*.in" EXCLUDE
> PATTERN ".gitignore" EXCLUDE
> )
Here's one of my earlier attempts:
PATTERN '*.in' EXCLUDE
PATTERN 'CMakeLists.txt' EXCLUDE
Is it possible that single qu
On Wed, Oct 15, 2014 at 6:49 PM, Dan Kegel wrote:
> The doc could use some more examples. I am having a hard
> time figuring out how to install a directory tree but exclude
> files matching .gitignore and Makefile.in.
This turned out to work for me:
install (
DIRECTORY ${samples_S
The doc could use some more examples. I am having a hard
time figuring out how to install a directory tree but exclude
files matching .gitignore and Makefile.in.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware
ect?
Which ones get run when?
On Fri, Sep 12, 2014 at 1:34 PM, Dan Kegel wrote:
> I'm porting a large project with many subdirectories from autotools to
> cmake and ctest.
> It's going well, but I ran into a question on how to do test setup/teardown.
> I've got CTEST_CU
I'd like to use CTestCustom.cmake to start a background job when tests
start, and kill it when tests finish.
Works great on Mac and Linux, but for some reason, on Windows ctest
wants to wait for
the background job to finish before starting the tests.
If I create CTestCustom.cmake containing
set(
On Mon, Sep 15, 2014 at 3:43 AM, David Cole wrote:
> What happens when you run VS "manually" as the buildbot user? Any
> warnings or errors?
VS never threw errors; only cmake itself did.
As the user 'buildbot', everything's peachy, the IDE is fine and
cmake doesn't output any errors. But th
I'm getting spurious errors like
error opening key: Software\Microsoft\VisualStudio\10.0\vsmacros\OtherProjects7
error opening key:
Software\Microsoft\VisualStudio\10.0\vsmacros\RecordingProject7
with cmake 3.0.1 and Visual Studio 2010 (but not 2013).
This was reported once before,
http://www.cma
I'm porting a large project with many subdirectories from autotools to
cmake and ctest.
It's going well, but I ran into a question on how to do test setup/teardown.
I've got CTEST_CUSTOM_PRE_TEST working nicely, but now I need different
conditions for each directory's worth of tests. Is there anyt
http://www.cmake.org/Wiki/CMake/Language_Syntax does explain
about semicolons, strings, and lists, but the consequences are
still kind of surprising. Newbies like me have to write little programs
to feel our way towards an understanding of what works.
For example, I wanted to pass a space-separat
If you leave off a doublequote somewhere, you will get confusing messages like
"CMake Warning (dev) in CMakeLists.txt:
Syntax Warning in cmake code at
/home/joe/foo/CMakeLists.txt:66:79
Argument not separated from preceding token by whitespace.
This warning is for project developers. Us
Hi! The simple CMakeLists.txt
cmake_minimum_required(VERSION 2.8)
project(foo)
enable_testing()
add_test(NAME bar COMMAND cmd /c echo hello)
fails for me when run on Windows 7 64 bit (only platform I've tried)
with ctest 2.8.12 or 2.8.11.
"ctest -V -C Debug" outputs
...
test 1
Start 1: bar
bly because the linker's being invoked twice in parallel on
>> the same file?).
>> See https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/423756
>>
>> On Fri, Jun 20, 2014 at 6:45 AM, Dan Kegel wrote:
>> > On Fri, Jun 20, 2014 at 3:02 AM, David Cole wrote:
>&g
.
See https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/423756
On Fri, Jun 20, 2014 at 6:45 AM, Dan Kegel wrote:
> On Fri, Jun 20, 2014 at 3:02 AM, David Cole wrote:
>>>> 138%
>>>> make -j4 all examples_noinst
>>
>>> I've seen this too but never
On Fri, Jun 20, 2014 at 3:02 AM, David Cole wrote:
>>> 138%
>>> make -j4 all examples_noinst
>
>> I've seen this too but never noticed a pattern about when it happens.
>
> Does it always happen when naming more than one target with make -j?
>
> I thought you were not supposed to name more than one
Seen in the wild today:
[119%] Building CXX object
CMakeFiles/clownCar.dir/examples_noinst/clownCar.C.o *
...
[138%] Built target examples_noinst
And on another machine, the last report was
[144%] Built target plasmasimple
All were with CMake 2.8.10.2
I see from
http://www.cmake.org/pipermail/
On Mon, May 26, 2014 at 8:04 AM, Klaim - Joël Lamotte wrote:
> - Why can't I use the install command from CMake? My understanding is that
> it's used to install the application in the system
Not really. It's to massage the installed files into their final form --
but not neccessarily into their
On Fri, May 23, 2014 at 4:38 PM, Eric Wing wrote:
> On 5/23/14, Dan Kegel wrote:
>> You can add the directory containing the 3rd party DLLs to the global
>> PATH environment variable, I bet.
>
> ... I just want a
> work-out-of-the-box solution with CMake doing local copi
You can add the directory containing the 3rd party DLLs to the global
PATH environment variable, I bet.
As for how to ship the Microsoft DLLs,
http://msdn.microsoft.com/en-us/library/ms235299.aspx
might be a good place to start reading?
- Dan
--
Powered by www.kitware.com
Please keep messages o
n it in the build tree and install tree?
>
> Izaak Beekman
> ===
> (301)244-9367
> UMD-CP Visiting Graduate Student
> Aerospace Engineering
> ibeek...@umiacs.umd.edu
> ibeek...@umd.edu
>
>
> On Sat, May 3, 2014 at 10:54 AM, Dan Kegel wrote:
>>
>> On Sat, May 3,
On Sat, May 3, 2014 at 7:17 AM, wrote:
> Use at least CMake 2.8.12 and in your library project add this:
> set(CMAKE_MACOSX_RPATH 1)
> ...
> For more details:
> http://www.kitware.com/blog/home/post/510
What he said. See also past discussion at
http://web.archiveorange.com/archive/v/5y7PkspCBZw
On Mon, Mar 31, 2014 at 7:13 AM, David Cole wrote:
> It will be cool to be able to build Metro apps using CMake.
Well, aside from the obvious problem :-)
--
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
FWIW, I tried making cmake projects that be used in two ways unchanged:
1) build installed libraries that other projects (not just cmake
projects) can use
2) be included in an overarching cmake project that knows about subprojects
but it did not turn out to be practical. Maybe I just hadn't drunk
Glad you got it working.
Am 26.12.2013 21:04 schrieb "Lorence Lombardo" :
> Hello Dan
>
> On 26/12/2013, you wrote:
>
> > cmake isn't the problem here. Did you make sure you could
> > compile hello, world with your wrapper?
> >
> > You may have to come up the unix shell learning curve a bit.
>
>
On Mon, Sep 30, 2013 at 11:04 AM, Dan Kegel wrote:
> If CMake is going to only
> behave properly when an argument is given in uppercase, it should
> abort if the argument is given in lowercase. Throw the users a bone!
> There is *no excuse* for forcing users to guess.
>
> I t
On Mon, Sep 30, 2013 at 10:29 AM, Williams, Norman K
wrote:
> I don't know why that is scary. It is the way CMake works, something that
> one must accomodate in order to use CMake.
I find it scary, annoying, and difficult to learn. If CMake is going to only
behave properly when an argument is gi
Our project depends on 53 different open soure packages,
all downloaded and built by a nice 900 line shell script.
(Build systems are so standardized that usually it's just one line to download,
build, and install a random open source project, yay!)
Yesterday I had the pleasure of coaxing it into b
On Tue, Sep 17, 2013 at 9:41 AM, James Bigler wrote:
> I have a static library I found using find_library. Typically with shared
> libraries I just link against the library and the dependencies come along
> for the ride.
>
> What is the prescribed way of doing this for static libraries?
How stat
On Sat, Sep 14, 2013 at 12:28 PM, adrian orozco wrote:
> It was a document with slides (either ppt or pdf). It talked about using
> build servers to deploy built artifacts and then downloading them later when
> some other projects needed them (or even test suites being run to test them)
> instead
I must have been looking at older doc somehow. Next time I'll include
a link to make my mistake even more obvious.
On Wed, Sep 11, 2013 at 4:37 PM, David Cole wrote:
> It's documented along with the CMAKE_INSTALL_PREFIX variable -- since 2.8.10
> according to the bug resolution.
>
>
> http://cma
I was mystified by the following problem:
add_executable(x x.c)
add_custom_command(
TARGET x
POST_BUILD
command sh ${CMAKE_SOURCE_DIR}/frob.sh x
)
Making this project didn't execute frob.sh.
Turns out cmake 2.8.9 silently ignores the command because... it's lowercase.
Writing COMMAND in
I was going to write a big post about how cmake doesn't support DESTDIR
( http://www.gnu.org/prep/standards/html_node/DESTDIR.html ),
but then I double checked, and it's even in the FAQ:
http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake.27s_.22make_install.22_support_DESTDIR.3F
Why had I never notice
On Tue, Sep 10, 2013 at 10:43 AM, Clinton Stimpson wrote:
> Using the INSTALL_RPATH property doesn't work correctly unless you use CMake
> 2.8.12 with the target property MACOSX_RPATH=1.
Done, example http://kegel.com/macosx/rpath/demo2/CMakeLists.txt
> If you want it to work with the older vers
All is well. I updated my minimal examples showing how to do it in
various worlds.
http://kegel.com/macosx/rpath/demo1/ - commandline gcc example
http://kegel.com/macosx/rpath/demo2/ - cmake 2.8.12 example
http://kegel.com/macosx/rpath/demo3/ - cmake 2.8.9 example
Someday I'll add a cross-pla
I had thought, from reading
http://www.kitware.com/blog/home/post/510
and the doc, that the only thing being added in 2.8.12 was
the MACOSX_RPATH variable.
I guess this is a documentation failure, and/or an example
of cmake's tendancy to accept and ignore garbage input.
cmake, bless its useful li
Howdy!
I'm using 2.8.9 installed on MacOSX using macports, and am trying to get
a minimal example of rpath working.
Doing it without cmake works fine; see
http://kegel.com/macosx/rpath/demo.txt
which just does
gcc -shared foo.c -install_name @rpath/foo.so -o foo.so
gcc -Wl,-rpath $OTHERDIR x
On Mon, Aug 26, 2013 at 12:16 PM, Thomas Taranowski
wrote:
> Now, I'm trying to implement a multi-stage build which does the following:
> 1) builds some external third-party dependencies.
> 2) auto-generate some code
> 3) build the source
> 4) package the result
>
> To do this, I'd like to implem
In projects that include a directory full of example programs that
don't usually need to be built,
it's convenient to have a phony target 'examples' that builds the examples.
add_custom_target looks like it's the way to implement phony targets, but the
doc confused me. It said targets created wit
On Wed, Jun 6, 2012 at 8:20 PM, Mikael Lyngvig wrote:
>> On Sun, May 6, 2012 at 4:58 PM, Rahul Garg wrote:
>> Just wondering, which version of CMake does "Mastering CMake 5th
>> edition" cover?
>
> Nobody seems to have answered this yet. A picture in the book shows CMake
> v2.6. I can't find an
On Wed, May 23, 2012 at 9:52 AM, Wiser, Tyson wrote:
> We don't modify external dependencies, but we do need to check them out and
> build them before building a library or executable that depends on them.
> Sometimes a developer will be working in a single library or executable.
> Sometimes he wi
On Wed, May 16, 2012 at 4:20 PM, Craig Scott
wrote:
> Don't give up just yet! There are other options which might meet your
> needs. No-one appears yet to have mentioned the LSB (Linux Standards Base)
> and it is designed to solve problems just like yours. Admittedly, it will
> take a little bit o
On Wed, May 16, 2012 at 1:32 PM, Eric Noulard wrote:
> You may have a look at OBS: https://build.opensuse.org/
> it may help you with "many-distro" building.
Probably worth trying just as a way to test compatibility,
even if you don't then ship the resulting packages.
I like the idea behind OBS,
On Wed, May 16, 2012 at 1:09 PM, Dan Kegel wrote:
> The source route *is* the best way possible, from the Linux point of view!
And yes, you should try hard to be compatible with the distros' versions
of all libraries (like Qwt). (Using a private copy of libraries is generally
frowned
Michael Jackson wrote:
> That was VERY informative. This is what I was afraid of. With Windows and OS
> X even though there are 3 or 4 versions if you build for the earliest one (XP
> or 10.5) the binary has a really good chance of still running on the latest
> (Win7 or Lion). With Linux and so
A commercial app might well use cmake to drive the linux packaging,
but if you want your app to become a first class citizen on Linux,
you should let the distros do the packaging. (Or better yet,
become a Debian developer and walk it through the process
yourself, but following the Debian way. Onc
On Mon, Jan 2, 2012 at 9:11 AM, David Cole wrote:
> Replies requested. Short replies only. Read on. Just a short reply
> with bug numbers or links to the bugs is all we need here.
Two easy ones (sorry they're late, but they're really small, and would
help java support on ubuntu):
http://public.ki
On Fri, Dec 23, 2011 at 1:00 PM, bmahf wrote:
> 2) The decision was made to go ahead with the build, even though it was
> going to be creating statis libraries, and then we would go back and fix
> that later. So I ran gmake and get to a subproject where the __solaris__
> define that I had given d
Aha, thanks for the explanation.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/files/v2.8/cmake-2.8.7-rc1-1-src.tar.bz2
seems to have DOS line endings, which leads the the following error
when running configure on linux:
/home/dank/Downloads/cmake-2.8.7/Bootstrap.cmk/cmConfigure.h:29:
error: missing terminating " character
The command
find . -type f -pr
On Thu, Dec 15, 2011 at 3:00 PM, Dan Kegel wrote:
> On Thu, Dec 15, 2011 at 6:57 PM, Dan Kegel wrote:
>> It seems that cmake-2.8.4's generator for eclipse falls short
>> when it comes to intellisense (er, content assist).
cmake trunk seems to do a nice job, without any of t
On Thu, Dec 15, 2011 at 6:57 PM, Dan Kegel wrote:
> It seems that cmake-2.8.4's generator for eclipse falls short
> when it comes to intellisense (er, content assist).
> While functions that are defined in the same source file are
> handled ok, functions in other files
It seems that cmake-2.8.4's generator for eclipse falls short
when it comes to intellisense (er, content assist).
While functions that are defined in the same source file are
handled ok, functions in other files don't seem to be.
Here's a simple example:
$ svn co http://winezeug.googlecode.com/sv
On Wed, Nov 16, 2011 at 9:43 AM, Alexander Neundorf
wrote:
>> I suspect that the only way to make source code control
>> plugins happy is to link to dummy projects like you
>> do for the main source directory.
>> And then there's no need for those individual source file links.
>
> AFAIK svn etc. w
On Tue, Nov 15, 2011 at 1:28 PM, Dan Kegel wrote:
> Tried it. It seems to get the linking right, though I'm not
> sure how excited my users are going to be about how
> deeply buried those source files are in the GUI. There's
> a whole lot of visual cruft around them.
W
On Mon, Nov 14, 2011 at 3:37 PM, Dan Kegel wrote:
> On Sat, Nov 12, 2011 at 11:04 AM, Alexander Neundorf
> wrote:
>> * please give current cmake master a try, it has several improvements.
>
> I'll give cmake master a spin sometime this week.
Tried it. It seems to get th
On Sat, Nov 12, 2011 at 11:04 AM, Alexander Neundorf
wrote:
> Ok. So two things:
> * please give current cmake master a try, it has several improvements.
> * please create a ticket in the cmake bug tracker for this, improved source-
> project generator for Eclipse, or something like this.
>
> My g
On Fri, Nov 11, 2011 at 11:01 PM, Dan Kegel wrote:
> I have no idea how to make that happen inside the cdt generator. I could
> kludge
> it in the shell script that runs cmake, but then it would break whenever
> the project was updated and cmake rebuilt the project automatical
In http://www.cmake.org/pipermail/cmake/2011-November/047250.html
I wrote
"I can't reorganize the source tree on the developers,
so I'm making do by putting the enclosing CMakeLists.txt next to all
the projects:
toplevel/trunk/CMakeLists.txt
which is checked out to
toplevel/CMakeLists.txt
It
On Fri, Nov 11, 2011 at 9:42 PM, Alexander Neundorf
wrote:
> So you imported the source project (and the build project), and now svn works
> for the source project ?
Right (I think). The symptom was that the source project would not import.
Now it does, reliably.
> Or does it also work in the b
On Fri, Nov 11, 2011 at 3:58 PM, Alexander Neundorf
wrote:
> What did you do ? Can you please explain exactly ? I'd really like to know.
I can't explain my previous problem - must have been stupid user error,
like being in wrong directory.
- Dan
--
Powered by www.kitware.com
Visit other Kitware
On Thu, Nov 10, 2011 at 2:32 PM, Dan Kegel wrote:
> http://www.cmake.org/Wiki/Eclipse_CDT4_Generator
> says the cdt generator should work with subclipse if you set
> -DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE
> on the commandline when running cmake, but it doesn't seem
>
Hey folks,
http://www.cmake.org/Wiki/Eclipse_CDT4_Generator
says the cdt generator should work with subclipse if you set
-DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE
on the commandline when running cmake, but it doesn't seem
to be working here.
As a sanity check, I verified that a normal eclipse p
On Wed, Nov 9, 2011 at 3:42 AM, David Cole wrote:
> I assume that your moving of the line related to "X11_Xv_INCLUDE_PATH"
> was unintentional, so I left it out of the above commit.
Yeah, that was sloppy of me, thanks.
This patch was hacked together on a live system,
but next time I'll take the
I needed this patch for an app I'm working on.
Only very lightly tested (i.e. my library loads now :-)
--- FindX11.cmake.old 2011-11-09 01:52:59.352674210 +
+++ FindX11.cmake 2011-11-09 01:56:23.047527447 +
@@ -33,6 +33,7 @@
#X11_XTest_INCLUDE_PATH,X11_XTest_LIB,
On Sun, Nov 6, 2011 at 9:34 AM, Eric Noulard wrote:
> Bug tracker has shown some weird error (seems disk space related) yesterday
> too.
When I posted yesterday, I got an out-of-disk-space error from the
mailing list at kitware,
so yeah, they seem to be having problems.
--
Powered by www.kitwar
On Sun, Nov 6, 2011 at 7:27 AM, Daniel Dekkers wrote:
> This "template" stuff should really be in the documentation, it would have
> helped me a lot.
> More than http://www.cmake.org/cmake/help/examples.html. A library called
> "Hello", really?
FWIW, I'm gathering more examples at
http://code.goo
1 - 100 of 128 matches
Mail list logo
