On Thu, Oct 7, 2010 at 9:55 PM, David Cole wrote:
> On Thu, Oct 7, 2010 at 5:34 PM, Campbell Barton
> wrote:
>>
>> On Thu, Oct 7, 2010 at 8:48 PM, Campbell Barton
>> wrote:
>> > On Thu, Oct 7, 2010 at 10:44 AM, Michael Wild wrote:
>> >>
>> >> On 7. Oct, 2010, at 11:58 , Campbell Barton wrote:
>
Hi,
I used to use CMake v2.6 on Cygwin-1.7 to build codes for MIPS.
It works well and my scripts like:
- CMakeLists.txt start -
CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
INCLUDE(CMakeForceCompiler)
SET(CMAKE_SYSTEM_NAME Generic)
# specify the cross compiler
CMAKE_FORCE_C_COMPILER(/cygdrive/c
Hi,
The FindwxWidget.cmake module in 2.8 is breaking the build of
MRIConvert [1] because it strips "-D" from the output of "wx-config
--cxxflags".
Is this not a bug?
This question was asked here last October [2] but not answered.
Thanks,
-Steve
[1] http://lcni.uoregon.edu/~jolinda/MRIConvert
Thanks!
On Thu, Oct 7, 2010 at 6:08 PM, Mark Moll wrote:
> On OS X, this command might be easier / faster:
>
> sysctl -n hw.ncpu
>
> On Oct 7, 2010, at 3:50 PM, David Cole wrote:
>
> > I just posted a short blog article demonstrating how to figure out the
> number of processors available for a "
On Thu, Oct 7, 2010 at 5:34 PM, Campbell Barton wrote:
> On Thu, Oct 7, 2010 at 8:48 PM, Campbell Barton
> wrote:
> > On Thu, Oct 7, 2010 at 10:44 AM, Michael Wild wrote:
> >>
> >> On 7. Oct, 2010, at 11:58 , Campbell Barton wrote:
> >>
> >>> Hi, I was wondering if this is possible or if it woul
tried that, no go
On Tue 05 Oct 21:44 2010 John Drescher wrote:
> On Tue, Oct 5, 2010 at 3:41 PM, e...@cs.bgu.ac.il wrote:
> > nope, like I wrote in the first post, I need a string spinbox so I've
> > extended qspinbox to support strings.
> > that is the custom widget in question.
> >
>
> You n
On Thu, Oct 7, 2010 at 8:48 PM, Campbell Barton wrote:
> On Thu, Oct 7, 2010 at 10:44 AM, Michael Wild wrote:
>>
>> On 7. Oct, 2010, at 11:58 , Campbell Barton wrote:
>>
>>> Hi, I was wondering if this is possible or if it would be acceptable
>>> to disable progress printout.
>>>
>>> At the momen
I'd rather make it as hard as possible to form bad habits. It would also be
helpful to me. I've moved to the console and typed "cmake ." several times
thinking I was in the build directory, and then cussed quite a bit while
digging through removing cruft. (Points on Version Control taken, I'll
I just posted a short blog article demonstrating how to figure out the
number of processors available for a "make -j" or a scripted ctest_build
call (with the "Unix Makefiles" generator) on Linux, Mac and Windows. Please
let me know if you have any ideas for how it might be improved or extended.
h
On Thursday 07 October 2010 21:32:51 Bill Hoffman wrote:
> The other issue is VS builds. At one point, I had some magic, cmake
> language to custom command converter thing going for this, but I am
> thinking it might be broken. If we did a pure custom-command version,
> it would work in the IDE'
On 10/7/2010 2:37 PM, Andreas Schneider wrote:
On Thursday 07 October 2010 18:57:50 Bill Hoffman wrote:
The java support was broken a while ago when we re-organized the build
trees. I don't have much time to work on this, but I would like to get
it fixed. The best approach might be a pure cus
On Thursday 07 October 2010 18:57:50 Bill Hoffman wrote:
> The java support was broken a while ago when we re-organized the build
> trees. I don't have much time to work on this, but I would like to get
> it fixed. The best approach might be a pure custom command approach.
Hi Bill,
with some m
You could try, though it makes my brain hurt to think about it. Why
go to such lengths to protect users from themselves?
On Thu, Oct 7, 2010 at 11:57 AM, wrote:
> Yeah, I think I'll go with something like what you are saying. I wonder
> if I can remove the CMakeFiles directory and the CMakeCac
On 10/7/2010 12:37 PM, Ryan Pavlik wrote:
On 10/07/2010 09:57 AM, Andreas Schneider wrote:
On Thursday 07 October 2010 16:45:49 Andreas Schneider wrote:
My current problem is with javah (C header file generator). This
generator
works on the class files. The class files aren't in
CMAKE_CURRENT
Yeah, I think I'll go with something like what you are saying. I wonder
if I can remove the CMakeFiles directory and the CMakeCache.txt file
from within the CMakeLists script...
Aaron C. Meadows
> Hi all.
>
>
>
> Is there a good way to disallow in-source builds? Ideally, I'd like
to
> prev
On 10/07/2010 09:57 AM, Andreas Schneider wrote:
On Thursday 07 October 2010 16:45:49 Andreas Schneider wrote:
My current problem is with javah (C header file generator). This generator
works on the class files. The class files aren't in
CMAKE_CURRENT_BINARY_DIR they are located in:
${CMAKE_C
On 10/7/2010 12:13 PM, kent williams wrote:
On Thu, Oct 7, 2010 at 11:05 AM, Bill Hoffman wrote:
What you want is for make to treat the external projects just like any other
library or executable in a build.
so, if you run this at the top of the build:
make -j4
It should run at most 4 concu
On Thu, Oct 7, 2010 at 11:05 AM, Bill Hoffman wrote:
>
> What you want is for make to treat the external projects just like any other
> library or executable in a build.
>
> so, if you run this at the top of the build:
>
> make -j4
>
> It should run at most 4 concurrent things at once for the whol
On 10/7/2010 11:52 AM, kent williams wrote:
1. Is that $(MAKE) or is it ${MAKE} ? One thing missing from the
CMake documentation -- unless I'm mistaken there's not much
explanation of CMake syntax in the documentation.
No, this is make syntax not CMake syntax.
2. I think it's probably not wha
On the other hand, with Visual Studio, it's all a big hairy mess.
because the setting for "how many parallel projects to build simultaneously"
is a single top level global setting. So when we spawn sub-VS instances in
VS 2008, for example, each one uses "N" for its parallel setting.
In that ca
If you use "$(MAKE)" in a BUILD_COMMAND, then the literal "$(MAKE)" appears
in the generated makefiles.
That tells the top level make to spawn sub-makes with the job controller
from the top level make.
Then you do not need to specify any -j flags anywhere except at the top
level.
And then, the t
1. Is that $(MAKE) or is it ${MAKE} ? One thing missing from the
CMake documentation -- unless I'm mistaken there's not much
explanation of CMake syntax in the documentation.
2. I think it's probably not what one intends to have 'make -j4' (for
example) used every time make is invoked. If you co
On 10/7/2010 11:25 AM, kent williams wrote:
On Wed, Oct 6, 2010 at 5:01 PM, Clifford Yapp wrote:
I use $(MAKE) in my BUILD_COMMAND and that seems to do OK, although I
don't know if it works universally.
That's an environment variable, as near as I can tell and isn't
mentioned in the current
On Wed, Oct 6, 2010 at 5:01 PM, Clifford Yapp wrote:
> I use $(MAKE) in my BUILD_COMMAND and that seems to do OK, although I
> don't know if it works universally.
>
That's an environment variable, as near as I can tell and isn't
mentioned in the current CMake documentation. So it's probably not t
On Thursday 07 October 2010 16:45:49 Andreas Schneider wrote:
> My current problem is with javah (C header file generator). This generator
> works on the class files. The class files aren't in
> CMAKE_CURRENT_BINARY_DIR they are located in:
>
> ${CMAKE_CURRENT_BINARY_DIR}/CMakeFiles/.dir///foo
> b
On Sunday 22 August 2010 22:11:28 Alexander Neundorf wrote:
> CMake "supports" Java, but that support is ... needs some work, there are
> some issues (I think this had to do with the location of the compiled
> files and the java packages or something).
> I assume patches to improve the situation wo
Two things: You should have your source code under version control,
for many reasons, but in this context:
1. The VC system can tell you which files are unknown to it, i.e.
those CMake pooped all over your source tree.
2. You can make sure your work is checked in, then delete the source
directory
On Thu, Oct 7, 2010 at 3:19 AM, Michael Wild wrote:
>
> On 6. Oct, 2010, at 20:10 , <
> aaron.mead...@thomsonreuters.com> wrote:
>
> > Hi all.
> >
> >
> >
> > Is there a good way to disallow in-source builds? Ideally, I'd like to
> > prevent it before any cruft is written into the source tree.
On 10/7/2010 8:21 AM, Thomas Sondergaard wrote:
I've got a reasonably big project with 30+ shared libraries and 70+
executables all in one cmake-based project. Today I changed one line in
a CMakeLists.txt in a sub-directory to link boost program_options in one
particular executable, and it caused
I've got a reasonably big project with 30+ shared libraries and 70+
executables all in one cmake-based project. Today I changed one line in
a CMakeLists.txt in a sub-directory to link boost program_options in one
particular executable, and it caused cmake to decide that it needed to
recompile e
On 10/07/2010 11:28 AM, Michael Wild wrote:
> function(add_test_executable name)
> add_executable(${name} EXCLUDE_FROM_ALL ${ARGN})
> if(NOT TARGET test-exes)
> add_custom_target(test-exes)
> endif()
> add_dependencies(test-exes ${name})
> endfunction()
>
> add_custom_target(check
>
Hi,I've tried to include assembler-files in one of my projects and with the
masm-rule I have included the sourcefiles like normal c++-files in my library
and enabled masm-support. But when I generate the visual studio 2010 solution
the files are included without a custom command to compile the f
On 7. Oct, 2010, at 11:58 , Campbell Barton wrote:
> Hi, I was wondering if this is possible or if it would be acceptable
> to disable progress printout.
>
> At the moment building with only minor changes prints a lot of text
> with CMake & Makefiles.
>
> eg:
> [ 4%] Built target bf_intern_aud
Hi, I was wondering if this is possible or if it would be acceptable
to disable progress printout.
At the moment building with only minor changes prints a lot of text
with CMake & Makefiles.
eg:
[ 4%] Built target bf_intern_audaspace
[ 4%] Built target bf_intern_string
[ 6%] Built target bf_in
On 07/10/10 10:21, fat...@crackmonkey.us wrote:
Then, to clear all CMake debris:
rm -r projectx/cmake/*
On Unix, if a project is managed by SVN it's easy to clean tree from
generated files:
$ svn-clean
Distributed with Debian, Ubuntu, etc. as well as downloadable [1]
I'm sure there are sim
On 7. Oct, 2010, at 10:54 , edA-qa mort-ora-y wrote:
> How can I have CMake not build test targets when doing a "make install"?
>
> I'd prefer that test targets are only ever built if "make test" is called.
>
> --
> edA-qa mort-ora-y
That needs a bit of trickery:
function(add_test_executable
> > is there an easy way to clean out a source tree if an in-source
> > build was accidentally kicked off? (short of dividing the files by
> > their timestamp and removing the newer ones, etc..)
My immediate thought was, does "make clean" not work for you? But I
guess you're talking about CMake d
How can I have CMake not build test targets when doing a "make install"?
I'd prefer that test targets are only ever built if "make test" is called.
--
edA-qa mort-ora-y
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
BigTPoker - Poker fun and games
Hi all,
As mentioned in my previous post, there is a bug in the cmake module
FindwxWidgets.cmake that prevents any library using wxWidgets to cross
compile for Windows from Linux. Lines 192 to 198 are concerned by this bug:
IF(WIN32 AND NOT CYGWIN AND NOT MSYS)
SET(wxWidgets_FIND_STYLE "win32")
On 6. Oct, 2010, at 20:10 ,
wrote:
> Hi all.
>
>
>
> Is there a good way to disallow in-source builds? Ideally, I'd like to
> prevent it before any cruft is written into the source tree. I
> experimented with writing a function into my CMakelists file and calling
> it. The function check
On 7. Oct, 2010, at 4:58 , Travis Jensen wrote:
> I'm trying to build a project using cmake (firebreath). I am stuck at a
> particular point (details later). I can build other projects without
> running into this problem. Other people can build firebreath without
> running into this problem.
41 matches
Mail list logo