On 20. Apr, 2010, at 23:37 , Brad King wrote:
> Alexander Neundorf wrote:
>> Hi,
>>
>> I have two small commits in my local cmake git repository.
>> Both are working, but I'd like to push only of them right now.
>> I haven't found out how to do this.
>> That's what I tried:
>>
>> ...
>> File .g
I am a novice with cmake dabbling with KDE4 and a little with blender) (on
X86_64(only) Linux. Some of our applications are installed in prefix /opt
For KDE4 compilation for example I noticed that libraries are detected (
reported correctly by cmake ) but often 'make' fails as the inc
On Tue, Apr 20, 2010 at 5:11 PM, Clinton Stimpson wrote:
> On Tuesday 20 April 2010 03:05:48 pm Timothy Shead wrote:
> > On 4/20/10 1:53 PM, Clinton Stimpson wrote:
> > >> Can you give me an example using DragNDrop to combine two CMake-built
> > >> executables into a single bundle? My impression
On Tuesday 20 April 2010 03:05:48 pm Timothy Shead wrote:
> On 4/20/10 1:53 PM, Clinton Stimpson wrote:
> >> Can you give me an example using DragNDrop to combine two CMake-built
> >> executables into a single bundle? My impression (perhaps dated) is that
> >> I'd have to do some magic around maki
On 4/20/10 1:53 PM, Clinton Stimpson wrote:
Can you give me an example using DragNDrop to combine two CMake-built
executables into a single bundle? My impression (perhaps dated) is that
I'd have to do some magic around making one of them a "source" file of
the other, so I could use MACOSX_PACKA
On Tue, Apr 20, 2010 at 3:53 PM, Clinton Stimpson wrote:
> On Tuesday 20 April 2010 12:59:42 pm Timothy Shead wrote:
> > On 4/20/10 12:53 PM, Clinton Stimpson wrote:
> > > On Tuesday 20 April 2010 11:44:27 am Timothy Shead wrote:
> > >> On 4/20/10 10:11 AM, Ben Medina wrote:
> > >>> What's throwin
To clarify, the patch I submitted saves you from debugging and figuring out
what the real problem is.
The actual solution is to use the last parameter of fixup_bundle() and pass in
"${QT_BINARY_DIR};${QT_LIBRARY_DIR}"
Clint
On Tuesday 20 April 2010 01:46:25 pm Clinton Stimpson wrote:
> I've a
On Tuesday 20 April 2010 12:59:42 pm Timothy Shead wrote:
> On 4/20/10 12:53 PM, Clinton Stimpson wrote:
> > On Tuesday 20 April 2010 11:44:27 am Timothy Shead wrote:
> >> On 4/20/10 10:11 AM, Ben Medina wrote:
> >>> What's throwing me off is the wiki says this about the Bundle
> >>> generator: "Ra
Hi Kent,
Have you tried to export the paths (to the dynamic libraries) before
making the package?
(Note it works on my project)
my 2cts,
Arnaud
On 04/20/2010 03:42 PM, kent williams wrote:
Well I found the magic incantation on OS X to get fixup_bundle work.
Now I'd like it to work on Linux.
I've already made a patch to fix this problem and put it in the bug tracker
(along with a couple other patches).
Clint
On Tuesday 20 April 2010 01:42:50 pm kent williams wrote:
> Well I found the magic incantation on OS X to get fixup_bundle work.
> Now I'd like it to work on Linux.
>
> What's
On Tuesday 20 April 2010, 罗勇刚 wrote:
> Patch for reserving spaces in predefined macros.
How did you create this patch ?
Looks very weird here:
ÿþd i f f - - g i t a / M o d u l e s / C M a k e F i n d E c l i p s e C
D T 4 . c m a k e b / M o d u l e s / C M a k e F i n d E c l i p s e C
Well I found the magic incantation on OS X to get fixup_bundle work.
Now I'd like it to work on Linux.
What's happening is I get many of these messages:
warning: cannot resolve item 'not'
The problem comes, as near as I can figure out, from when ldd is run
to discover the library prerequisites.
On 2010-04-20 03:27, Michael Hertling wrote:
On 04/19/2010 10:07 PM, Benoit Thomas wrote:
I'm using an external library which is already compiled. I have wrapped
the library in a MyLib.cmake and use it in cmake as an imported library.
It works fine, but since the include line uses relative
On Tuesday 20 April 2010, 罗勇刚 wrote:
> Well, can you give me the right to commit?
No, I can't, I don't have the access to these parts to do that.
> Then I can commit a series of patches. or it's to noise.
You could get a login at http://gitorious.org, create a clone of the cmake
project, push y
On 4/20/10 12:53 PM, Clinton Stimpson wrote:
On Tuesday 20 April 2010 11:44:27 am Timothy Shead wrote:
On 4/20/10 10:11 AM, Ben Medina wrote:
What's throwing me off is the wiki says this about the Bundle
generator: "Rationale: de-facto standard mechanism for distributing
bundles." Unless that's
On Tuesday 20 April 2010 11:44:27 am Timothy Shead wrote:
> On 4/20/10 10:11 AM, Ben Medina wrote:
> > What's throwing me off is the wiki says this about the Bundle
> > generator: "Rationale: de-facto standard mechanism for distributing
> > bundles." Unless that's only specifically referencing the
On 4/20/10 10:11 AM, Ben Medina wrote:
What's throwing me off is the wiki says this about the Bundle
generator: "Rationale: de-facto standard mechanism for distributing
bundles." Unless that's only specifically referencing the previous
sentence about distributing a compressed disk image.
Which
The Bundle generator is a (sort of silly) "create a bundle from a command
line executable at packaging time" mechanism. You do not want to use it
unless that is exactly what you are trying to do.
If you're building a regular Mac Bundle application and you already have
your Bundle built at build ti
Of course you are right. I just scanned the directory too fast.
Thanks. I am taking some ideas from the UseLatex.cmake file as I am
originally having DOxygen generate the LaTex files, then have the
pdf2tex to convert the file as needed.
Thanks for all the help
--
Mike Jackson
On Apr 20, 2
FindLATEX.cmake has been part of CMake for many years now. It should be in
2.6.4.
-Ken
On 4/20/10 9:29 AM, "Michael Jackson" wrote:
Must have been CMake 2.8. I'm still using 2.6.4. I guess I should move
up one day..
--
Mike Jackson
On Apr 20, 2010, at 11:17 AM, Moreland, Kenneth wrote:
That seems to be how everyone does it, so I guess I'll follow suit.
What's throwing me off is the wiki says this about the Bundle
generator: "Rationale: de-facto standard mechanism for distributing
bundles." Unless that's only specifically referencing the previous
sentence about distributing a comp
Must have been CMake 2.8. I'm still using 2.6.4. I guess I should move
up one day..
--
Mike Jackson
On Apr 20, 2010, at 11:17 AM, Moreland, Kenneth wrote:
CMake comes with a FindLATEX.cmake module that will find the latex,
pdflatex, and related files. I have also posted a group of macros
On 04/20/2010 10:45 AM, Clinton Stimpson wrote:
What can I do to fix this? Alternatively, is there a better way to
create symlinks on install?
You can use configure_file() to create the script with the variables
expanded,
Clint
Since there was more to be added, I opted for the configure_file
CMake comes with a FindLATEX.cmake module that will find the latex, pdflatex,
and related files. I have also posted a group of macros that makes it quite
easy to create CMake builds for LaTeX files. The link is below.
http://www.cmake.org/Wiki/CMakeUserUseLATEX
-Ken
On 4/20/10 9:05 AM, "Mic
On 4/20/10 6:09 AM, Matthias Goesswein wrote:
Hello!
I`m using the Softune-Compiler under CMake with MSYS on Windows. (I'v
e written the Plattform files by myself)
The Softune Compiler (For Fujitsu Microcontrollers) requires
Backslashes for paths in the options, but Cmake generates slashes as
Does anyone have a Find*.cmake file that would find LaTex by any
chance and be willing to share it?
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software
On 04/20/2010 08:26 AM, Michael Surette wrote:
I am using CMake 2.8.1 and have the following in my main CMakeLists.txt
---
install(DIRECTORY ${FLTK_SOURCE_DIR}/FL
DESTINATION ${PREFIX_INCLUDE} USE_SOURCE_PERMISSIONS
PATTERN ".svn" EXCLUDE
)
if(CMAKE_HOST_UNIX)
install(SCRIPT ${FLTK
I am using CMake 2.8.1 and have the following in my main CMakeLists.txt
---
install(DIRECTORY ${FLTK_SOURCE_DIR}/FL
DESTINATION ${PREFIX_INCLUDE} USE_SOURCE_PERMISSIONS
PATTERN ".svn" EXCLUDE
)
if(CMAKE_HOST_UNIX)
install(SCRIPT ${FLTK_SOURCE_DIR}/CMake/install-symlinks.cmake)
endif
Hello!
I`m using the Softune-Compiler under CMake with MSYS on Windows. (I'v e
written the Plattform files by myself)
The Softune Compiler (For Fujitsu Microcontrollers) requires Backslashes
for paths in the options, but Cmake generates slashes as it is usual in
MSYS.
e.g.
The linker must b
Hello Michael,
The usual way is to do it just the other way around, and that's also how CMake
does it. Instead of defining DEBUG for debug builds, it defines NDEBUG for
release builds. So, in your code do:
#ifndef NDEBUG
printf("THIS IS DEBUG INFORMATION\n");
#endif
Thank you for the tip..
On 20. Apr, 2010, at 10:31 , Mathieu Dubois wrote:
> Hello,
>
> I'm a new CMake user under Linux and I like it.
>
> I have a simple question concerning CMAKE_C_FLAGS_DEBUG.
>
> I have made a library and I would like it to print more information when
> compiled when CMAKE_BUILD_TYPE=Debug.
> I
Hello,
I'm a new CMake user under Linux and I like it.
I have a simple question concerning CMAKE_C_FLAGS_DEBUG.
I have made a library and I would like it to print more information when
compiled when CMAKE_BUILD_TYPE=Debug.
I think that the best way is to define a DEBUG preprocessor variable an
Hello -,
I want to use Msing32-library on Windows
FIND_LIBRARY(MSIMG32_LIBRARY Msimg32)
If I run the cmake-gui it cannot find the library.
There are no problems if cmake runs "inside the visual studio".
Are there some enviroment variables I have to set for the gui-version?
Micha
___
Hello!
I've submitted the bug report
(http://public.kitware.com/Bug/view.php?id=10577)
I also added an example project, which uses the gnu assembler, so you
could reproduce the problem.
Cheers,
Matthias.
Am 19.04.2010 22:32, schrieb Alexander Neundorf:
On Friday 16 April 2010, Matthias G
On 04/19/2010 10:07 PM, Benoit Thomas wrote:
> I'm using an external library which is already compiled. I have wrapped
> the library in a MyLib.cmake and use it in cmake as an imported library.
> It works fine, but since the include line uses relative path, it changes
> from projects to project
35 matches
Mail list logo
