> The code is in Source/cmDependsC.cxx.
> I think it's already quite optimized, but feel free to have a look at it :-)
Thanks, I'll have a look.
--
Best regards, Pavel
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://
On 13. Jan, 2010, at 1:55 , Nico Schlömer wrote:
> Pheeew..
> So I've now been trying to include one *single* library from an
> external project (liba.a) into my own project, writing FindA.cmake.
> Somehow I still fail to apply the dependencies correctly. What I do is
>
> [...]
> ADD_LIBRARY(A S
On Tue, Jan 12, 2010 at 2:04 PM, Bill Hoffman wrote:
>
> What version of the compiler did you install? The commercial versions of
> the compiler have a VS command prompt under the tools menu that you can use
> to create a shell with the correct env to run the compiler.
>
> The same is true for th
Pheeew..
So I've now been trying to include one *single* library from an
external project (liba.a) into my own project, writing FindA.cmake.
Somehow I still fail to apply the dependencies correctly. What I do is
[...]
ADD_LIBRARY(A STATIC IMPORTED)
SET_TARGET_PROPERTIES( A PROPERTIES
Hmmm, I'll dig a little deeper to see what's hapening.
Thanks,
-dan
On 1/12/10 4:25 PM, "Bill Hoffman" wrote:
> Daniel Blezek wrote:
>> Hi Mike,
>>
>> Sorry, I guess I wasn't quite clear. The re-builds occur when I touch any
>> CMakeLists.txt file in the entire project. Since we're under
Daniel Blezek wrote:
Hi Mike,
Sorry, I guess I wasn't quite clear. The re-builds occur when I touch any
CMakeLists.txt file in the entire project. Since we're under active
development, new source files are being added fairly frequently. I didn't
want re-builds to trigger each time a develop
Hi Mike,
Sorry, I guess I wasn't quite clear. The re-builds occur when I touch any
CMakeLists.txt file in the entire project. Since we're under active
development, new source files are being added fairly frequently. I didn't
want re-builds to trigger each time a developer adds a new class.
I noticed that it generates the following output:
-- Check if this is a free VC compiler - yes
I do not think I am using a free VC compiler, something is wrong here.
Is it possible to use nmake with Visual Studio 2008 compiler using cmake
2.8?
Are you running cmake from a shell that has the
> I noticed that it generates the following output:
> -- Check if this is a free VC compiler - yes
> I do not think I am using a free VC compiler, something is wrong here.
> Is it possible to use nmake with Visual Studio 2008 compiler using cmake
> 2.8?
>
I just tested this on my build box and sim
> > Did you try the Nmake generator and call
> >
> > nmake help
> >
> Thanks, I tried using nmake generator i.e. - cmake ../ -G "NMake
Makefiles"- but
> it does not work in cmake 2.8. It fails to find the compiler. However
the
> command - cmake ../ -G "Visual Studio 9 2008" - works fine. The err
Alexander Neundorf schrieb:
...
So indeed a relative CMAKE_INSTALL_PREFIX is interpreted relative to the build
dir.
Do you think this should be handled differently ?
Then c:/usr would have to be translated at some point to "/c:/usr" if cross
compiling on some UNIX.
Would this make sense ?
Al
you shouldn't have to do that. There are multitudes of projects that
do exactly what you are doing and don't have continuous rebuilds. Now,
having said that I am _assuming_ that osconfig.h.in is NOT being
changed, generated, updated or in any way changed? osconfig.h.in being
changed would c
On Tue, Jan 12, 2010 at 02:09:36PM -0600, Daniel Blezek wrote:
> CONFIGURE_FILE(${DCMTK_SOURCE_DIR}/osconfig.h.in
>${DCMTK_BINARY_DIR}/include/dcmtk/config/osconfig.h)
>
> However, every time I touch a CMake file, ³osconfig.h² is regenerated,
> causing nearly the entire library to
We have a large-ish system. Deep within an included utility class, I have
this code:
CONFIGURE_FILE(${DCMTK_SOURCE_DIR}/osconfig.h.in
${DCMTK_BINARY_DIR}/include/dcmtk/config/osconfig.h)
However, every time I touch a CMake file, ³osconfig.h² is regenerated,
causing nearly the enti
On Tuesday 12 January 2010, Pavel Shevaev wrote:
> On Mon, Jan 11, 2010 at 11:53 PM, Alexander Neundorf
>
> wrote:
> > On Monday 11 January 2010, Pavel Shevaev wrote:
> >> On Sat, Dec 26, 2009 at 2:20 PM, Pavel Shevaev
> >
> > wrote:
> >> > Guys, what is the best way to to make the dependency sca
On Mon, Jan 11, 2010 at 11:53 PM, Alexander Neundorf
wrote:
> On Monday 11 January 2010, Pavel Shevaev wrote:
>> On Sat, Dec 26, 2009 at 2:20 PM, Pavel Shevaev
> wrote:
>> > Guys, what is the best way to to make the dependency scanner ignore some
>> > paths?
>
> how long does it take if you don't
Hi,
I have searched a lot for a way to use cmake in a xbox360 environment, but have
not found any answers.
I want to use cmake to generate the .vcproj environment for developing on the
xbox 360 and on PS3. On PS3 it seems quite easy because you only need to define
the VSI integration pre-pro
Hi,
I've started running nightly cmake tests and submitting them to your
dashboard. I was hoping the nightly tests would pick up this problem
I'm having. When compiling Fortran90 code with pathscale-3.2
(pathf90), I get this error.
pathf90 ERROR parsing -J../module: unknown flag
I think that's a fine idea, but I will leave it to whomever maintains the
Module in CMake.
-Ken
On 1/12/10 12:55 AM, "Michael Wild" wrote:
On 11. Jan, 2010, at 22:26 , Moreland, Kenneth wrote:
> I have a simple Fortran program that uses MPI that I am trying to configure
> with CMake. The
Hi Brad,
issue number is 10126: http://www.cmake.org/Bug/view.php?id=10126
Haven't had much time to add a patch, sorry.
Thanks,
Johannes
2010/1/12 Brad King
> Johannes Felten wrote:
> > I took a look at the CMake 2.8.0 sourcecode and tracked it down to
> > Source/kwsys/ProcessUNIX.c in funct
Johannes Felten wrote:
> I took a look at the CMake 2.8.0 sourcecode and tracked it down to
> Source/kwsys/ProcessUNIX.c in function kwsysProcessSetupOutputPipeFile I
> believe.
> I wonder why CMake sets the permissions explicitly to 644 here. Is this
> a bug or done intentionally?
Nice find; it's
Hello,
Am Freitag, 8. Januar 2010 schrieb Marcel Loose:
> If you've set the flags "-foo -bar" using add_definitions(), instead of
> manipulating CMAKE_C_FLAGS directly, you can use
>
> set_directory_properties(PROPERTIES COMPILE_DEFINITIONS "-baz")
Currently I manually set CMAKE_Fortran_FLAGS_D
22 matches
Mail list logo
