date:20120124

Re: [CMake] [New Module] Arduino CMake

2012-01-24 Thread Alfa Omega

2012/1/24 Alexander Neundorf 

> Hi,
>
> On Tuesday 24 January 2012, Alfa Omega wrote:
> > Hi,
> >
> > What part does not follow the convention? I'm using a toolchain file,
> plus
> > when I was writing this I based it on a existing module bundled with
> CMake
> > (but cant remember which).
> >
> > I'm open to modifying my project to match the convention. If you could
> > point out which parts don't quite meet the convention, I would greatly
> > appreciate that.
>
> The functions in ArduinoProcessing.cmake should have a common prefix to
> show
> where they come from, e.g. ARDUINO_
>
ArduinoProcessing.cmake is a prototype, and isn't used with Arduino CMake,
so you can ignore that.


> Same for the functions in FindArduino.cmake
> The documentation for the functions should be at the top of the file, so
> when
> cmake generates documentation, it will be included.
>
The documentation for the module is located at the top (only those two
function should be used), all other function are for internal use (but are
documented).

setup_arduino_compiler() looks wrong.
>
What do you mean by it looks wrong (the name might not be the best :))?


> Did you consider adding Arduino as "operating system" ?
> Then you could add a
> Platforms/Arduino.cmake
> which is loaded automatically when CMAKE_SYSTEM_NAME is set to Arduino.
>
Ah, I just see, you did.
> Is there are reason why you didn't put all the functions, settings, etc.
> there
> ?
> Then it wouldn't be necessary to use FindArduino.cmake when you already
> know
> you are building for Arduino.
> (e.g. there is no FindWindows.cmake, you simply are on Windows, or the
> cmake
> run fails).
>
That is a good point, but then how could I specify that I want a specific
minimal version?

The toolchain file should be mostly done after the first three set() calls
> you
> have. More or less all of the rest should be in Arduino.cmake or
> Arduino-GNU-
> C/CXX.cmake.
>
> The functions for setting up additional targets look ok.
>
> What should find_sources() be used for ?
>
It's used for getting all the sources located at specified path, because
there is some processing of the sources (for Arduino library detection
based on the header includes).

This looks out of place.
>
> Thanks
> Alex
>



-- 

--=[QTZ]=--
QueezyTheGreat
--

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/mailman/listinfo/cmake

Re: [CMake] compiler flags visual studio

2012-01-24 Thread Klaim - Joël Lamotte

On Tue, Jan 24, 2012 at 14:33, Tom Deblauwe wrote:

> Hello,
>
> What compiler flags do you need to enable if you want to use the
> possibility to have something like this in your code:
>
> char Image[width(), height()];
>
> This worked before with my compiler(visual studio 2005) but not with the
> cmake generated project. It complains about expecting a constant
> expression. Anybody knows?
>
>
That is not valid C or C++ code (once they were standardized at least).
Just use * instead of , and it will do what I guess you want. I think the
code didn't do what you wanted before...

Joël Lamotte
--

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/mailman/listinfo/cmake

Re: [CMake] Top level directory with component install

2012-01-24 Thread Eric Noulard

2012/1/22 Eric Noulard :
> 2012/1/13 Eric Noulard :
>
>> Hi everybody I just reviewed the patch from Daniel and it seems fine to me
>> BUT including this would change the default cpack behavior for all
>> Archive Generators
>> (ZIP, TGZ, STGZ, TBZ2) when doing component install.
>>
>> The "new" behavior is more consistent with the non-component behavior but
>> the two has been different since 2.8.4 so I'd like to know whether if
>> people are relying
>> on it or if we may change such default behavior which may be viewed as 
>> flawed...
>>
>> Please have a look at:
>> http://public.kitware.com/Bug/view.php?id=12129
>> and comment here.
>>
>> I'd like to have feedback before pushing this to next.
>> Currently it is in stage/AddTopLevelForComponent.
>
> No feedback for more than a week.
> No scream either.
> Just pushed to next.

Feedback on this is NEEDED before it gets merged to master.
http://public.kitware.com/Bug/view.php?id=12129#c28402

Please comment here or on the bug tracker.


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
--

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/mailman/listinfo/cmake

Re: [CMake] fixup_bundle & already-fixed-up dependencies

2012-01-24 Thread Michael Jackson

I think you need to feed BundleUtilities another argument that lists where to 
find the ogre frameworks. I think.
___
Mike JacksonPrincipal Software Engineer
BlueQuartz SoftwareDayton, Ohio
mike.jack...@bluequartz.net  www.bluequartz.net

On Jan 24, 2012, at 1:53 PM, Nikolay Kasyanov wrote:

> Hi,
> I'm trying to use fixup_bundle on OS X.
> I had following problem with some of my dependencies (Ogre game engine & 
> OIS): they already have @executable_path in it (so, they already fixed up), 
> so in my executable there is no absolute path to library, so fixup_bundle 
> cannot find & copy Ogre's framework into bundle during fixup.
> 
> Here is otool output for Ogre.framework:
> otool -L /Library/Frameworks/Ogre.framework/Versions/1.7.3/Ogre
> /Library/Frameworks/Ogre.framework/Versions/1.7.3/Ogre:
>   @executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre 
> (compatibility version 0.0.0, current version 1.7.3)
>   /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 
> (compatibility version 2.0.0, current version 152.0.0)
>   /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 
> (compatibility version 1.0.0, current version 15.0.0)
>   /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 
> 1.2.3)
>   /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current 
> version 7.9.0)
>   /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 
> 832.0.0)
>   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 125.2.0)
>   /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 
> 227.0.0)
>   
> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 
> (compatibility version 150.0.0, current version 550.29.0)
>   /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 
> (compatibility version 300.0.0, current version 751.29.0)
>   /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 
> (compatibility version 45.0.0, current version 1038.32.0)
> 
> Here is otool output for my executable:
> otool -L OpenMW.app/Contents/MacOS/openmw 
> OpenMW.app/Contents/MacOS/openmw:
>   @executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre 
> (compatibility version 0.0.0, current version 1.7.3)
>   @executable_path/../Frameworks/OIS.framework/Versions/A/OIS 
> (compatibility version 1.0.0, current version 1.0.0)
>   /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL 
> (compatibility version 1.0.0, current version 1.0.0)
>   /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 
> (compatibility version 2.0.0, current version 152.0.0)
>   /usr/X11/lib/libfreetype.6.dylib (compatibility version 13.0.0, current 
> version 13.2.0)
>   /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current 
> version 52.0.0)
>   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 125.2.11)
>   
> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 
> (compatibility version 150.0.0, current version 550.43.0)
>   
> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
>  (compatibility version 1.0.0, current version 38.0.0)
> 
> Can it be solved somehow? 
> --
> 
> 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/mailman/listinfo/cmake

--

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/mailman/listinfo/cmake

Re: [CMake] [New Module] Arduino CMake

2012-01-24 Thread Alexander Neundorf

Hi,

On Tuesday 24 January 2012, Alfa Omega wrote:
> Hi,
> 
> What part does not follow the convention? I'm using a toolchain file, plus
> when I was writing this I based it on a existing module bundled with CMake
> (but cant remember which).
> 
> I'm open to modifying my project to match the convention. If you could
> point out which parts don't quite meet the convention, I would greatly
> appreciate that.

The functions in ArduinoProcessing.cmake should have a common prefix to show 
where they come from, e.g. ARDUINO_
Same for the functions in FindArduino.cmake
The documentation for the functions should be at the top of the file, so when 
cmake generates documentation, it will be included.

setup_arduino_compiler() looks wrong.
Did you consider adding Arduino as "operating system" ?
Then you could add a 
Platforms/Arduino.cmake
which is loaded automatically when CMAKE_SYSTEM_NAME is set to Arduino.
Ah, I just see, you did.
Is there are reason why you didn't put all the functions, settings, etc. there 
?
Then it wouldn't be necessary to use FindArduino.cmake when you already know 
you are building for Arduino.
(e.g. there is no FindWindows.cmake, you simply are on Windows, or the cmake 
run fails).
The toolchain file should be mostly done after the first three set() calls you 
have. More or less all of the rest should be in Arduino.cmake or Arduino-GNU-
C/CXX.cmake.

The functions for setting up additional targets look ok.

What should find_sources() be used for ?
This looks out of place.

Thanks
Alex
--

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/mailman/listinfo/cmake

[CMake] fixup_bundle & already-fixed-up dependencies

2012-01-24 Thread Nikolay Kasyanov

Hi,
I'm trying to use fixup_bundle on OS X.
I had following problem with some of my dependencies (Ogre game engine & OIS): 
they already have @executable_path in it (so, they already fixed up), so in my 
executable there is no absolute path to library, so fixup_bundle cannot find & 
copy Ogre's framework into bundle during fixup.

Here is otool output for Ogre.framework:
otool -L /Library/Frameworks/Ogre.framework/Versions/1.7.3/Ogre
/Library/Frameworks/Ogre.framework/Versions/1.7.3/Ogre:
@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre 
(compatibility version 0.0.0, current version 1.7.3)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 
(compatibility version 2.0.0, current version 152.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 
(compatibility version 1.0.0, current version 15.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 
1.2.3)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current 
version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 
832.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 125.2.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 
227.0.0)

/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 
(compatibility version 150.0.0, current version 550.29.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 
(compatibility version 300.0.0, current version 751.29.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 
(compatibility version 45.0.0, current version 1038.32.0)

Here is otool output for my executable:
otool -L OpenMW.app/Contents/MacOS/openmw 
OpenMW.app/Contents/MacOS/openmw:
@executable_path/../Frameworks/Ogre.framework/Versions/1.7.3/Ogre 
(compatibility version 0.0.0, current version 1.7.3)
@executable_path/../Frameworks/OIS.framework/Versions/A/OIS 
(compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL 
(compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 
(compatibility version 2.0.0, current version 152.0.0)
/usr/X11/lib/libfreetype.6.dylib (compatibility version 13.0.0, current 
version 13.2.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current 
version 52.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
version 125.2.11)

/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 
(compatibility version 150.0.0, current version 550.43.0)

/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
 (compatibility version 1.0.0, current version 38.0.0)

Can it be solved somehow? 
--

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/mailman/listinfo/cmake

[CMake] Check compiler flags

2012-01-24 Thread Tim Gallagher

Hi,

Is there a module for CheckFortranCompilerFlag? I see one for C and CXX, but 
not one for Fortran.

Tim
--

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/mailman/listinfo/cmake

Re: [CMake] Complex problem : recursive dependency configurations

2012-01-24 Thread Robert Dailey

Have I gone and confused everybody on this? :P

-
Robert Dailey


On Mon, Jan 23, 2012 at 6:01 PM, Robert Dailey  wrote:

> As you know, in target_link_libraries(), you can specify "debug",
> "optimized", or "general" to specify which configurations a library will be
> applied to.
>
> I have developed a system to allow dependencies to recursively add their
> own dependencies. Suppose we have 3 targets:
>
> A:
>   libx
>   liby
>   libz
>
> B:
>   foo
>   bar
>   A
>
> C:
>   A
>   B
>
>
> Above, I list each target (A, B, C). The items under it are the targets it
> depends on. So, target A depends on targets named libx, liby, and libz.
> Similarly, target B depends on targets foo, bar, and A.
>
> When I flatten out all of the dependencies for target C, it looks like so:
>
> A
> B
> libx
> liby
> libz
> foo
> bar
>
> This is pretty simple, but each dependency listed can also have a "debug",
> "release", or "general" next to it. So let's use the same example as last
> time, but introduce some of these prefixes:
>
> A:
>   libx
>   liby
>   libz
>
> B:
>   foo
>   bar
>   A
>
> C:
>   debug B
>
> Above, since "B" is listed as "debug", library B and all of its
> dependencies should only build in the debug configuration. So when we
> flatten this out, you will see the following. Note that this flattened list
> is what is sent to target_link_libraries()
>
> debug B
> debug foo
> debug bar
> debug A
> debug libx
> debug liby
> debug libz
>
> Now where this REALLY gets confusing, is when we have a mixture of
> "conflicts", where the same target is specified as a dependency twice, but
> with different configuration prefixes:
>
>
> A:
>   libx
>   liby
>   libz
>
> B:
>   foo
>   bar
>   A
>
> C:
>   optimized A
>   debug B
>
> In this case, A's dependencies are specified as optimized, but B's are
> specified as debug, but B also depends on A, so A's dependencies would be
> debug as well.
>
> I need to implement a system that can handle such conflicts and resolve
> them appropriately. For example, the way A's dependencies would be resolved
> is by specifying them as "general" or no prefix at all, since the flattened
> list includes them both in debug and optimized. So the final, flattened
> list would look like:
>
> A
> debug B
> libx
> liby
> libz
> debug foo
> debug bar
>
> This is VERY complex and due to the way lists work and stuff, I can't
> think of how to do this. Any tips?
>
> -
> Robert Dailey
>
--

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/mailman/listinfo/cmake

Re: [CMake] Packaging DEB at different directory with CPack

2012-01-24 Thread Damián Nohales

Many thanks Eric! your explanation really helps me!

El 24/01/12 04:21, Eric Noulard escribió:
> 2012/1/24 Damián Nohales :
>> Hello,
>>
>> I'm doing an application for Debian based systems and I need to package
>> a .deb file, my application has several files to install in addition to
>> the main executable.
>>
>> So, my CMakeLists.txt file looks like:
>>
>> 
>> project("myapp" C)
>> cmake_minimum_required(VERSION 2.8)
>>
>> # The executable
>> add_executable(myapp main.c)
>> install(TARGETS myapp RUNTIME DESTINATION bin)
> 
> this is ok.
> 
>>
>> # Another file to install
>> install(FILES ${CMAKE_SOURCE_DIR}/data/myapp.desktop DESTINATION
>> "${CMAKE_INSTALL_PREFIX}/share/applications")
> 
> This is usually wrong as it is an absolute PATH destination
> why don't you simply specify
> install(FILES ${CMAKE_SOURCE_DIR}/data/myapp.desktop DESTINATION
>  share/applications)
> 
>> SET(CPACK_GENERATOR "DEB")
>> SET(CPACK_DEBIAN_PACKAGE_MAINTAINER "Damián Nohales")
>>
>> INCLUDE(CPack)
>> 
>>
>> I execute CMake and build the package in this way:
>>
>> 
>> $ cd build
>> $ cmake -DCMAKE_INSTALL_PREFIX=install ..
> 
> Specifying CMAKE_INSTALL_PREFIX has no effect on the following CPack call
> 
>> $ make package
>> 
>>
>> I need to specify a prefix for the installation because I want to test
>> the application without installing on my whole system.
> 
> Then you should override CPACK_PACKAGING_INSTALL_PREFIX
> 
> $ cd build
> $ cpack -D CPACK_PACKAGING_INSTALL_PREFIX=$HOME/testinstall -G DEB
> 
> another possibility is to install you deb content at an alternate location
> using
> 
> dpkg --instdir=$HOME/testinstall -i your.deb
> 
> 
>> But the .deb content resulting of executing "make package" is not what I
>> expected:
>>
> 
> [...]
> 
>>
>> Well, I'm sure you are understanding the problem, I'm expecting that the
>> generated .deb package to has the files under the /usr directory having
>> too the myapp.desktop file under the following filename
>> "/usr/share/applications/myapp.desktop".
>>
>> Any suggestion?
> 
> Always use relative DESTINATION install path unless you forcibly want
> an ABSOLUTE destination.
> 
--

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/mailman/listinfo/cmake

Re: [CMake] visual studio macros

2012-01-24 Thread David Cole

>From the CMake source code file Source/cmGlobalVisualStudio8Generator.cxx:

//
std::string cmGlobalVisualStudio8Generator::GetUserMacrosDirectory()
{
  // Some VS8 sp0 versions cannot run macros.
  // See http://support.microsoft.com/kb/928209
  const char* vc8sp1Registry =
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\8.0\\"
"InstalledProducts\\KB926601;";
  const char* vc8exSP1Registry =
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\VisualStudio\\8.0\\"
"InstalledProducts\\KB926748;";
  std::string vc8sp1;
  if (!cmSystemTools::ReadRegistryValue(vc8sp1Registry, vc8sp1) &&
  !cmSystemTools::ReadRegistryValue(vc8exSP1Registry, vc8sp1))
{
return "";
}


Since you mention you have SP1 installed, (KB926601), we skip copying
the macros files for your installation since we know they will not
work. We also will not even try to call the macro, even if you copy it
into place by hand. See the Microsoft URL in the source code comment
for more details...

If you want to try to use this functionality anyway, you'll have to
modify CMake's code to avoid the return statement in the above code.


HTH,
David


On Tue, Jan 24, 2012 at 5:10 AM, Tom Deblauwe  wrote:
> Hello,
>
> I'm running a Windows 7 64 bit OS, and I'm using visual studio 2005 with
> service pack 1. Below is the list of versions. Now my question is: how can I
> manually check that all macro stuff works and is configured correctly? In
> other words: how can I install the macro's manually? They are definitely not
> showing up automaticaly in the "macro explorer". Also, when is the time that
> CMake installs those macros in visual studio? Is it when the project files
> are generated or at install time of cmake itself? How are the macros then
> eventually run, what triggers them?
>
> Best regards,
> Tom,
>
> Microsoft Visual Studio 2005
> Version 8.0.50727.867  (vsvista.050727-8600)
> Microsoft .NET Framework
> Version 2.0.50727 SP2
> Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1
> (KB926601)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB2251481)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB2465367)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB2538218)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB2548826)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB937061)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB971023)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB971090)
> Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB973673)
> Update for Microsoft Visual Studio 2005 Professional Edition - ENU
> (KB932232)
>
> --
> Tom Deblauwe
> R&D Engineer
>
> Traficon International N.V.
> Vlamingstraat 19
> B-8560 Wevelgem
> Belgium
> Tel.: +32 (0)56 37.22.00
> Fax: +32 (0)56 37.21.96
> URL: www.traficon.com
>
> --
>
> 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/mailman/listinfo/cmake
--

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/mailman/listinfo/cmake

Re: [CMake] compiler flags visual studio

2012-01-24 Thread John Drescher

On Tue, Jan 24, 2012 at 8:33 AM, Tom Deblauwe  wrote:
> Hello,
>
> What compiler flags do you need to enable if you want to use the possibility
> to have something like this in your code:
>
> char Image[width(), height()];
>
> This worked before with my compiler(visual studio 2005) but not with the
> cmake generated project. It complains about expecting a constant expression.
> Anybody knows?
>

No compiler flags support that.

John
--

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/mailman/listinfo/cmake

[CMake] Conditional CFLAG for armv6 only - Xcode, iOS

2012-01-24 Thread James Munro

Hi there,

I'm using CMake as part of a workflow on various iOS projects. I have a 
question regarding setting a conditional compiler flag dependent on the 
architecture being compiled:

Apple LLVM causes a serious bug when compiling for older devices that require 
the armv6 architecture. The solution is to disable Thumb support for this 
architecture, but to keep it active for armv7 (using -mno-thumb). A description 
of the compiler issue is here, for those interested: 
http://wanderingcoder.net/2010/07/19/ought-arm/ 

I can set this globally in CMake using: set (CMAKE_C_FLAGS "-mno-thumb"). 
However, I would like to do this only for the armv6 architecture. Setting this 
up through Xcode is easy using a "conditional build setting", see here for 
details: 
http://stackoverflow.com/questions/8390606/is-there-a-way-to-compile-for-arm-rather-than-thumb-in-xcode-4

We use CMake to generate our Xcode projects, and then we work from this 
projects on a daily basis. However, we treat the projects as temporary 
scratchpads and often regenerate them from scratch as part of our workflow. Is 
it possible to mimic this Xcode conditional build setting through my CMake 
configuration so that we don't need to do it manually through Xcode?

Just in case anyone was wondering, iOS app binaries generally contain both 
armv6/7 code, so creating a project for one or the other is not an option.

Any help is greatly appreciated.

James Munro, Programmer, Kwalee Ltd
E: james.mu...@kwalee.com

--

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/mailman/listinfo/cmake

[CMake] compiler flags visual studio

2012-01-24 Thread Tom Deblauwe


Hello,

What compiler flags do you need to enable if you want to use the 
possibility to have something like this in your code:


char Image[width(), height()];

This worked before with my compiler(visual studio 2005) but not with the 
cmake generated project. It complains about expecting a constant 
expression. Anybody knows?


Best regards,
Tom,

--

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/mailman/listinfo/cmake

Re: [CMake] CTest: Glob files to include in coverage report with 0% line coverage

2012-01-24 Thread David Cole

On Tue, Jan 24, 2012 at 2:51 AM, Eric Noulard  wrote:
> 2012/1/24 Rolf Eike Beer :
>> Andreas Schuh wrote:
>>> Hi,
>>>
>>> Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
>>> used to add additional files which shall be included in the coverage
>>> report. This is useful to ensure that files which are not covered by
>>> any test are still reported with 0% line coverage.
>>
>> Oh, interesting variable. How can it be that there is absolutely zero
>> documentation for in CMake?
>
> Because ctest and cpack documentation are very far from being
> documented as cmake is ?
> E.g. current ctest and cpack do not have --help-variable-* support?
>
> If you want to help please try my "stage/ImproveCPackDoc-reloaded" branch
> and may be read this: http://public.kitware.com/Bug/view.php?id=10067
>
> The technique I propose may be used for cpack, ctest, etc...
>
> --
> Erk
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
> --
>
> 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/mailman/listinfo/cmake


There is zero documentation for all of the ctest related variables. We
need somebody who can write a bunch of documentation someday to fill
in that blank.
--

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/mailman/listinfo/cmake

Re: [CMake] How to define dependencies? Problem with nmake builds.

2012-01-24 Thread David Cole

On Tue, Jan 24, 2012 at 1:40 AM, james  wrote:
> My component source list includes:
>
>    easyrtd.src/COMRtdInterface.cpp
>    easyrtd.src/EasyRTD.rc
>    easyrtd.src/EasyRTD.idl
>
> and after fixing up the paths Visual Studio builds the project OK.
>
> However, nmake does not - the RC compiler runs before MIDL.
>
> It seems that there is a dependency that's missing.  This would seem to be
> the implied one from the TYPELIB statement in the RC file.
>
> Is it enough to use OBJECT_DEPENDS on the rc file (treating the implied res
> file as an object) naming the tlb that would be output by midl?
>
> Presumably I'd also have to declare that the idl file produces the tlb file,
> using OBJECT_OUTPUTS? (Or not?  This is only for Makefile generators, but
> how is the OBJECT_DEPENDS going to be handled in other cases?)
>
> There seems to be an element of magic going on here rather than explicitly
> handling the midl/rc/link toolchain. I know Visual Studio tries to make this
> stff easy - but how does it work with nmake (and ideally the mingw toolchain
> too)?
>
> James
> --
>
> 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/mailman/listinfo/cmake

Unlike rc and C++, we have not defined a "language" for IDL files.
That's why it doesn't work out of the box for the NMake Makefiles (or
any other makefile) generator. Sounds like a shortcoming in the
"support for IDL files" that we added, only considering Visual Studio
users as the primary target audience.

So... the answer to your question is that it probably doesn't work
with NMake Makefiles, at least for now. Further work required...


:-(

Sorry,
David
--

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/mailman/listinfo/cmake

[CMake] visual studio macros

2012-01-24 Thread Tom Deblauwe


Hello,

I'm running a Windows 7 64 bit OS, and I'm using visual studio 2005 with 
service pack 1. Below is the list of versions. Now my question is: how 
can I manually check that all macro stuff works and is configured 
correctly? In other words: how can I install the macro's manually? They 
are definitely not showing up automaticaly in the "macro explorer". 
Also, when is the time that CMake installs those macros in visual 
studio? Is it when the project files are generated or at install time of 
cmake itself? How are the macros then eventually run, what triggers them?


Best regards,
Tom,

Microsoft Visual Studio 2005
Version 8.0.50727.867  (vsvista.050727-8600)
Microsoft .NET Framework
Version 2.0.50727 SP2
Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1 
(KB926601)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB2251481)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB2465367)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB2538218)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB2548826)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB937061)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB971023)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB971090)
Security Update for Microsoft Visual Studio 2005 Professional Edition - 
ENU (KB973673)
Update for Microsoft Visual Studio 2005 Professional Edition - ENU 
(KB932232)


--
*Tom Deblauwe*
*R&D Engineer*

Traficon International N.V.
Vlamingstraat 19
B-8560 Wevelgem
Belgium
Tel.: +32 (0)56 37.22.00
Fax: +32 (0)56 37.21.96
URL: www.traficon.com 
--

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/mailman/listinfo/cmake

Re: [CMake] no rule to make target ' ' needed by- with RCpp and not mysql++

2012-01-24 Thread pasparis



I find the problem it was the name of the library: libRcpp.so instead of libRCpp.so
 Message d'origine 
De : paspa...@noos.fr
À : cmake@cmake.org
Objet : [CMake] no rule to make target ' ' needed by- with RCpp and not mysql++
Date : 24/01/2012 10:10:01 CET

Hellosereral days ago I got from Eric in the mail list the way to link mysql++ in kdevelop with cmake. it works fine but as soon asI want to do the same thing with RCpp and RInside two libraries which manage a link between C++ and the R software when I compile the main prog I getmake[3]: *** No rule to make target `/usr/lib/R/site-library/Rcpp/lib/libRCpp.so', needed by `pkdr1'.  Stop.I don't understand why thanks in advance if someone could help meCMakeList Library file (which uses msql++ and RInside)project(pliba)include_directories(/usr/include)include_directories(/usr/include/mysql)include_directories(/usr/include/mysql++)include_directories(/usr/lib/R/site-library/Rcpp/include)include_directories(/usr/lib/R/site-library/RInside/include)include_directories(/home/pascal/pKDR1/pLibA/Include)add_library(pliba STATIC test_RInside.cpp)target_link_libraries(pliba  /usr/lib/libmysqlpp.a)target_link_libraries(pliba  /usr/lib/libmysqlclient.a)target_link_libraries(pliba  /usr/lib/i386-linux-gnu/libz.so)target_link_libraries(pliba  /usr/lib/R/lib/libR.so)target_link_libraries(pliba  /usr/lib/R/site-library/Rcpp/lib/libRCpp.so)target_link_libraries(pliba  /usr/lib/R/site-library/RInside/lib/libRInside.so)CMakeList program file which uses the librarycmake_minimum_required(VERSION 2.8)project(pkdr1)add_subdirectory(pLibA)include_directories (${PROJA_SOURCE_DIR}/pLibA) add_executable(pkdr1 main.cpp)target_link_libraries(pkdr1 pliba)


--

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/mailman/listinfo/cmake

[CMake] no rule to make target ' ' needed by- with RCpp and not mysql++

2012-01-24 Thread pasparis



Hellosereral days ago I got from Eric in the mail list the way to link mysql++ in kdevelop with cmake. it works fine but as soon asI want to do the same thing with RCpp and RInside two libraries which manage a link between C++ and the R software when I compile the main prog I getmake[3]: *** No rule to make target `/usr/lib/R/site-library/Rcpp/lib/libRCpp.so', needed by `pkdr1'.  Stop.I don't understand why thanks in advance if someone could help meCMakeList Library file (which uses msql++ and RInside)project(pliba)include_directories(/usr/include)include_directories(/usr/include/mysql)include_directories(/usr/include/mysql++)include_directories(/usr/lib/R/site-library/Rcpp/include)include_directories(/usr/lib/R/site-library/RInside/include)include_directories(/home/pascal/pKDR1/pLibA/Include)add_library(pliba STATIC test_RInside.cpp)target_link_libraries(pliba  /usr/lib/libmysqlpp.a)target_link_libraries(pliba  /usr/lib/libmysqlclient.a)target_link_libraries(pliba  /usr/lib/i386-linux-gnu/libz.so)target_link_libraries(pliba  /usr/lib/R/lib/libR.so)target_link_libraries(pliba  /usr/lib/R/site-library/Rcpp/lib/libRCpp.so)target_link_libraries(pliba  /usr/lib/R/site-library/RInside/lib/libRInside.so)CMakeList program file which uses the librarycmake_minimum_required(VERSION 2.8)project(pkdr1)add_subdirectory(pLibA)include_directories (${PROJA_SOURCE_DIR}/pLibA) add_executable(pkdr1 main.cpp)target_link_libraries(pkdr1 pliba)


--

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/mailman/listinfo/cmake

Re: [CMake] About CMAKE_INSTALL_PREFIX - solved

2012-01-24 Thread pellegrini


Great, thanks a lot Rolf & Michael

Rolf Eike Beer a écrit :

Hello everbody,

I would like to understand a bit more one feature related to
CMAKE_INSTALL_PREFIX initialization.

When reading the documentation, it is specified that this variable


contains the directory that will be pre-pended to all install
  

directories and that it should be defaulted to C:/Program Files on


Windows. However, in my current build the variable is not defaulted to
C:/Program Files but to C:/Program Files/libcrysfml where "crysfml " is
the name of my base project.
  

This unexpected feature (at least to my understanding !) leads me to my


second question.
  

I would like to get rid of the "crysfml " subdirectory in the value of


CMAKE_INSTALL_PREFIX. I could obvioulsy
  

use:
get_filename_component(MY_CMAKE_INSTALL_PREFIX
${CMAKE_INSTALL_PREFIX} PATH)
but this would fail if CMAKE_INSTALL_PREFIX is set on the cmake command


line by the user because, in such case, the installation will not be
done in the directory that he provided but in its parent directory.
Rather counter-intuitive.
  

What I would need is a mechanism to detect whether the
CMAKE_INSTALL_PREFIX has been set or not by the user on the
command-line. If so, I take directly the values he provided, and if not


so, I take the parent directory of the default value.
  

Is that possible ?



if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
 ...
endif ()

Eike


--

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/mailman/listinfo/cmake
  



--
Eric Pellegrini
Calcul Scientifique
Institut Laue-Langevin
Grenoble, France

--

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/mailman/listinfo/cmake

Re: [CMake] About CMAKE_INSTALL_PREFIX

2012-01-24 Thread Rolf Eike Beer

> Hello everbody,
>
> I would like to understand a bit more one feature related to
> CMAKE_INSTALL_PREFIX initialization.
>
> When reading the documentation, it is specified that this variable
contains the directory that will be pre-pended to all install
> directories and that it should be defaulted to C:/Program Files on
Windows. However, in my current build the variable is not defaulted to
C:/Program Files but to C:/Program Files/libcrysfml where "crysfml " is
the name of my base project.
>
> This unexpected feature (at least to my understanding !) leads me to my
second question.
>
> I would like to get rid of the "crysfml " subdirectory in the value of
CMAKE_INSTALL_PREFIX. I could obvioulsy
> use:
> get_filename_component(MY_CMAKE_INSTALL_PREFIX
> ${CMAKE_INSTALL_PREFIX} PATH)
> but this would fail if CMAKE_INSTALL_PREFIX is set on the cmake command
line by the user because, in such case, the installation will not be
done in the directory that he provided but in its parent directory.
Rather counter-intuitive.
>
> What I would need is a mechanism to detect whether the
> CMAKE_INSTALL_PREFIX has been set or not by the user on the
> command-line. If so, I take directly the values he provided, and if not
so, I take the parent directory of the default value.
>
> Is that possible ?

if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
 ...
endif ()

Eike


--

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/mailman/listinfo/cmake

Re: [CMake] About CMAKE_INSTALL_PREFIX

2012-01-24 Thread Michael Wild

On 01/24/2012 09:35 AM, pellegrini wrote:
> Hello everbody,
> 
> I would like to understand a bit more one feature related to
> CMAKE_INSTALL_PREFIX initialization.
> 
> When reading the documentation, it is specified that this variable
> contains the directory that will be pre-pended to all install
> directories and that it should be defaulted to C:/Program Files on
> Windows. However, in my current build the variable is not defaulted to
> C:/Program Files but to C:/Program Files/libcrysfml where "crysfml " is
> the name of my base project.
> 
> This unexpected feature (at least to my understanding !) leads me to my
> second question.
> 
> I would like to get rid of the "crysfml " subdirectory in the value of
> CMAKE_INSTALL_PREFIX. I could obvioulsy
> use:
>get_filename_component(MY_CMAKE_INSTALL_PREFIX
> ${CMAKE_INSTALL_PREFIX} PATH)
> but this would fail if CMAKE_INSTALL_PREFIX is set on the cmake command
> line by the user because, in such case, the installation will not be
> done in the directory that he provided but in its parent directory.
> Rather counter-intuitive.
> 
> What I would need is a mechanism to detect whether the
> CMAKE_INSTALL_PREFIX has been set or not by the user on the
> command-line. If so, I take directly the values he provided, and if not
> so, I take the parent directory of the default value.
> 
> Is that possible ?
> 
> thanks a lot
> 
> Eric
> 
> 
> 

You can use the variable CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT to
determine whether the cache contains the default value or has been
modified by the user. E.g.

project(Foo)
if(WIN32 AND CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
  set(CMAKE_INSTALL_PREFIX "${CMAKE_GENERIC_PROGRAM_FILES}" CACHE PATH
"Install path prefix, prepended onto install directories." FORCE)
endif()

should do what you want.

HTH

Michael
--

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/mailman/listinfo/cmake

[CMake] About CMAKE_INSTALL_PREFIX

2012-01-24 Thread pellegrini


Hello everbody,

I would like to understand a bit more one feature related to 
CMAKE_INSTALL_PREFIX initialization.


When reading the documentation, it is specified that this variable 
contains the directory that will be pre-pended to all install 
directories and that it should be defaulted to C:/Program Files on 
Windows. However, in my current build the variable is not defaulted to 
C:/Program Files but to C:/Program Files/libcrysfml where "crysfml " is 
the name of my base project.


This unexpected feature (at least to my understanding !) leads me to my 
second question.


I would like to get rid of the "crysfml " subdirectory in the value of 
CMAKE_INSTALL_PREFIX. I could obvioulsy

use:
   get_filename_component(MY_CMAKE_INSTALL_PREFIX 
${CMAKE_INSTALL_PREFIX} PATH)
but this would fail if CMAKE_INSTALL_PREFIX is set on the cmake command 
line by the user because, in such case, the installation will not be 
done in the directory that he provided but in its parent directory. 
Rather counter-intuitive.


What I would need is a mechanism to detect whether the 
CMAKE_INSTALL_PREFIX has been set or not by the user on the 
command-line. If so, I take directly the values he provided, and if not 
so, I take the parent directory of the default value.


Is that possible ?

thanks a lot

Eric



--
Eric Pellegrini
Calcul Scientifique
Institut Laue-Langevin
Grenoble, France

--

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/mailman/listinfo/cmake

Re: [CMake] [New Module] Arduino CMake

2012-01-24 Thread Alfa Omega

Hi,

Support for Teamcity is available, but not publicly accessible. I have a
patched version of CMake/CTest which has a special flag that enables
Teamcity service messages. I use it internally at my company, but I want to
integrate it into CMake (so that I don't have have a custom build of
CMake). Test aggregation works perfectly. I also have a CMake module to
that simplifies emitting Teamicty service messages.

Tomasz B.



On Tue, Jan 24, 2012 at 8:31 AM, Johan Björk  wrote:

> Hi Alfa,
>
> We are really interested in the teamcity + CTest support. Is that
> available somewhere already?
>
> Thanks
> /Johan
>
>
> On Sun, Jan 22, 2012 at 7:51 PM, Alfa Omega wrote:
>
>> Hi everyone,
>>
>> I'm not quite sure what the correct procedure is for becoming a CMake
>> contributor, but from what I've read I should send a email here if I want
>> to add a new module to cmake.
>>
>> For the past year I've been hosting my CMake modules on GitHub (
>> https://github.com/queezythegreat/arduino-cmake) and the project is
>> mature enough that it could be included into CMake. The project is called
>> Arduino CMake and it adds support for building Arduino projects. It is a
>> alternative to the Arduino IDE, and works on Windows, Linux and Mac.
>>
>> The project is growing and getting more and more users, and I think it's
>> would be a god fit to start bundling it with CMake. The project is well
>> documented both from a developer standpoint as well as the user side.
>>
>> So what are the steps I should take in order to integrate my project into
>> CMake?
>>
>> I also would like to contribute back some extensions to the CMake, such
>> as Teamcity support for CTest. Any information would be greatly
>> appreciated.
>>
>> Tomasz Bogdal
>>
>> --
>>
>> 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/mailman/listinfo/cmake
>>
>
>


-- 

--=[QTZ]=--
QueezyTheGreat
--

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/mailman/listinfo/cmake

Re: [CMake] [New Module] Arduino CMake

Re: [CMake] compiler flags visual studio

Re: [CMake] Top level directory with component install

Re: [CMake] fixup_bundle & already-fixed-up dependencies

Re: [CMake] [New Module] Arduino CMake

[CMake] fixup_bundle & already-fixed-up dependencies

[CMake] Check compiler flags

Re: [CMake] Complex problem : recursive dependency configurations

Re: [CMake] Packaging DEB at different directory with CPack

Re: [CMake] visual studio macros

Re: [CMake] compiler flags visual studio

[CMake] Conditional CFLAG for armv6 only - Xcode, iOS

[CMake] compiler flags visual studio

Re: [CMake] CTest: Glob files to include in coverage report with 0% line coverage

Re: [CMake] How to define dependencies? Problem with nmake builds.

[CMake] visual studio macros

Re: [CMake] no rule to make target ' ' needed by- with RCpp and not mysql++

[CMake] no rule to make target ' ' needed by- with RCpp and not mysql++

Re: [CMake] About CMAKE_INSTALL_PREFIX - solved

Re: [CMake] About CMAKE_INSTALL_PREFIX

Re: [CMake] About CMAKE_INSTALL_PREFIX

[CMake] About CMAKE_INSTALL_PREFIX

Re: [CMake] [New Module] Arduino CMake

23 matches

Site Navigation

Mail list logo

Footer information