riables that was set in some sh file ?
What I usually do is rewrite the sh file into a proper CMake package and
then use find_package() to pull it in. Another option is of course to
just include() it.
/M
--
Magnus Therning OpenPGP: 0x927912051716CE39
email: mag...@therning.org ja
will have
access to everything you need if you set "CMAKE_EXPORT_COMPILE_COMMANDS"
and then look at the resulting `compile_commands.json`.
/M
--
Magnus Therning OpenPGP: 0x927912051716CE39
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe
Bruce Stephens writes:
> Looks like https://github.com/redguardtoo/cpputils-cmake might be involved...
If that is the case then this section could be of interest:
https://github.com/redguardtoo/cpputils-cmake#stop-creating-makefiles-for-flymake
/M
--
Magnus Therning Open
d error. The test
> should fail for any other return value or if anything is written to
> stdout or if anything else is written to stderr.
>
> Howto, please?
I'd wrap it in a shell script, or use something like shelltestrunner[1].
/M
[1]: http://joyful.com/shelltestrunn
lity to set dependencies for add_custom_command in POST_BUILD
> mode;
> 2) add possibility to populate list of targets if we have specified ones in
> list.
>
> Or maybe correct me if I miss something.
Have you not simply missed add_test()? ;)
What's the reason for wanting the tests t
ies and link them conventionally, but I'd like to make this path
> shortening method work.
Wouldn't a better solution be to use an options file, something like
ld's @file[1]?
/M
[1]: http://linux.die.net/man/1/ld
--
Magnus Therning OpenPGP: 0x927912051716CE39
emai
vakano writes:
> Hi,
>
> I have some link option as below:
>
> -Wl, -rpath, ${PROJECT_TOP}/dist ../proj_a/lib_a.a -lb -Wl, --whole-archive
> ../proj_c/lib_c.a
What have you tried?
/M
--
Magnus Therning OpenPGP: 0x927912051716CE39
email: mag...@therning
he other flags. If I change my
~CMakeLists.txt~ to instead contain
#+BEGIN_SRC cmake
set(CMAKE_C_FLAGS "-std=gnu11 -Wall -Wextra -Wpedantic -Werror")
#+END_SRC
Then I don't get those C99-related warnings. Is there some way to get
~CMAKE_C_STANDARD~ to put ~-std=gnu11~ /bef
Ruslan Baratov writes:
> On 22-Dec-15 04:07, Magnus Therning wrote:
>> Ruslan Baratov writes:
>>
>>> On 20-Dec-15 01:31, Magnus Therning wrote:
>>>> Ruslan Baratov writes:
>>>>
>>>>> How about using RelWithDebInfo? See:
>>&
uilt with `-g` and stuff built without it. I'm
also *not* mixing linking with debug- and non-debug libraries.
I'm only mixing stuff build with `-DNDEBUG` and stuff built without it.
/M
--
Magnus Therning OpenPGP: 0x927912051716CE39
email: mag...@therning.org jabber: mag
Ruslan Baratov writes:
> On 20-Dec-15 01:31, Magnus Therning wrote:
>> Ruslan Baratov writes:
>>
>>> How about using RelWithDebInfo? See:
>>> http://stackoverflow.com/a/28124715/2288008
>> Hmm, I'm probably missing something but how does that solve the
Dave Flogeras writes:
> On Fri, Dec 18, 2015 at 9:55 AM, Magnus Therning wrote:
>>
>> I'm sure I'm not the first one to run into the conflict between a
>> desire to test the code shipped to customers and the desire to at the
>> same time define NDEBUG to mak
/M
> On 18-Dec-15 20:55, Magnus Therning wrote:
>> I'm sure I'm not the first one to run into the conflict between a desire
>> to test the code shipped to customers and the desire to at the same time
>> define NDEBUG to make sure tests don't have their `assert` tur
remove -DNDEBUG from the CFLAGS for tests (possibly by
defining a new macro, `ADD_EXECUTABLE_TEST()` or something). Another
option is to `#undef NDEBUG` in the source of tests.
If there's some more or less standard way to address this I'd like to
use that.
/M
--
Magnus Ther
ing. :) Sometimes CMake feels clean and
convenient, and then all of a sudden one has to start thinking about
what's available at which state and frustration grows... I guess build
systems are a bit like mail readers, they all suck, one just have to
find one that sucks less than the previous o
.txt in the parent dir
to lib&src with
set(foobarSRCS lib/foo.c lib/bar.c)
(maybe with the use of CMAKE_CURRENT_SOURCE_DIR too).
A final questin, why was it a convenience lib in the autotools setup?
Unless there's really a need to compile the files multiple times the
whole
eak, but then I quickly ran
into the problem of finding the effective CFLAGS used for a
source/target.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
Finagle's Sixth L
r, it doesn't work with e.g. Ninja (to pick just one).
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
Don't worry about other people stealing your ideas. If
rently overwriting the cached value from CMakeCInformation.cmake. I
> can't write a line like "set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Os")" because
> then the result is "-std=c99 -std=c99 -Os" for the second project.
>
> Any help would be greatly appreciated
t; source directories. I want to use the project 2 cmake files to build it.
Have a look at ExternalProject
(http://www.cmake.org/cmake/help/v2.8.12/cmake.html#module:ExternalProject)
it's very likely what you are looking for.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
32bit compat
> libraries out of the box (let alone older machines which have no
> such compat libs at all)
>
> So can we please get 64bit Linux binaries for the next CMake
> release?
What 64-bit Linux distribution, that doesn't package CMake, do you
use?
/M
--
Magnus Thernin
ituation where
you're looking for the answer to some question, but all you can find
is other people asking the same question in various fora. By
answering your own question you'll help other people avoid that
irritating situation when they are looking around for an answer to
this particul
On Wed, Dec 11, 2013 at 11:44 PM, Jacob Avraham
wrote:
> Hi,
> I'm running on a 32bit Linux and I'd like to build from the same source,
> libraries complied and linked as 32bit and 64bit.
> They should be installed in /usr/lib and /usr/lib64.
> How do I go about and do that?
Personally I've neve
; done with python/bat/cmake/ any scripting language.
With a proper editor you can even do while writing the CMakeLists.txt
file.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning
ially make it a bit more manageable by identifying
a self-contained subset of one app and the libraries it depends on.
Once you've done that it should be easy to see how to scale it up to
cover the entire project.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag
> # Minimal toolchain file:
> SET(CMAKE_SYSTEM_NAME Linux)
> SET(CMAKE_SYSTEM_PROCESSOR "armv7")
> SET(CMAKE_C_COMPILER arm-none-eabi-gcc)
The only way I found around this was
set(CMAKE_SYSTEM_NAME Generic )
but I think that is exactly what you want to avoid given your
Visual Studio
10.0/VC/bin/link.exe
vcvarsall.bat location = C:/Program Files (x86)/Microsoft Visual Studio
10.0/VC/vcvarsall.bat
I'd consider that a terrible hack though, so hopefully there's someone
else with a better idea.
/M
--
Magnus Therning OpenPGP
rect environment?
> Should I put a call to vcvarsall.bat in the command line? Is there
> a CMake variable that has the path to that?
I would expect that you need to put the folder where nmake.exe lives
in the %PATH%, the easiest way of achieving that is probably to use
vcvarsall.bat.
/M
--
Magnus T
es with a directory
> structure like in the first example above?
I may be missing something, but from the view of the unpacker of the
TGZ-ball the two are equivalent, right? So why do you prefer the
'./x/...' over 'x/...'?
/M
--
Magnus Therning OpenP
It does indeed work properly, once one uses the correct
path in all places.
Sorry for the noise!
/M
On Fri, Nov 15, 2013 at 11:02 PM, Magnus Therning wrote:
> On Fri, Nov 15, 2013 at 04:45:23PM -0500, Brad King wrote:
>> On 11/15/2013 04:17 PM, Magnus Therning wrote:
>> > I
On Fri, Nov 15, 2013 at 04:45:23PM -0500, Brad King wrote:
> On 11/15/2013 04:17 PM, Magnus Therning wrote:
> > I just reproduced it locally. Here's what I did:
>
> I tested with a local share and corresponding url template:
>
> file:127.0.0.1/share$/%(algo)/%(
On Wed, Nov 13, 2013 at 10:26:53AM -0500, Brad King wrote:
> On 11/13/2013 03:59 AM, Magnus Therning wrote:
>> On Tue, Nov 12, 2013 at 5:09 PM, Brad King wrote:
>>> Add to ExternalData_URL_TEMPLATES the entry
>>>
>>> file:share.host/foo/bar/%(algo)/%(hash)
On Tue, Nov 12, 2013 at 5:09 PM, Brad King wrote:
> On 11/12/2013 08:43 AM, Magnus Therning wrote:
>> Is there some way to point to an unmounted Windows share?
>
> Add to ExternalData_URL_TEMPLATES the entry
>
> file:share.host/foo/bar/%(algo)/%(hash)
That still fai
weren't more independent and it's
disappointing to find that it isn't possible to use an UNC path to
download a data object.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http:/
bar/%(algo)/%(hash)" work. For the former
ExternalData reports
"unsupported protocol"
and for the latter
"URL using bad/illegal format or missing URL"
Is there some way to point to an unmounted Windows share?
/M
--
Magnus Therning OpenPGP: 0
ce group.
>
>
>
> How can I achieve both my goals?
>
>
>
> Thanks in advace!
>
>
> --
>
> 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
e VS-project-config Debug
(which is default for CMake), but I did expect the above to put
mymsproj in the VS-project-config LibDebug. What am I doing wrong
here?
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe
ried it on OSX, but it
> should hopefully be an OK starting point. (If not - hack away at my
> answer!)
There's also a recent thread of mine on this list that's at least
slightly related:
http://www.cmake.org/pipermail/cmake/2013-October/056086.html
/M
--
Magnus Therning
IES
IMPORTED_LOCATION ${CMAKE_BINARY_DIR}/gtest-build/libgtest.a
IMPORTED_LINK_INTERFACE_LIBRARIES -lpthread
INTERFACE_INCLUDE_DIRECTORIES ${PROJECT_SOURCE_DIR}/gtest/include
)
And all I need a user of the library to do is
target_link_libraries(one_test gtest)
On Sat, Oct 19, 2013 at 11:28:53AM +0400, Игорь Пашев wrote:
> 2013/10/19 Magnus Therning :
> > Is it possible to put the include path in some property on the library
> > as well, to avoid using a separate variable for that?
>
> SET_TARGET_PROPERTIES (target PROPERTIES )
Of
On Wed, Oct 16, 2013 at 11:36:53PM +0200, Alexander Neundorf wrote:
> On Wednesday 16 October 2013, Magnus Therning wrote:
>> When defining a library via add_library() it's possible to link
>> against it by just putting its name into target_link_libraries().
>> Is there
ld -lgtest -lpthread
)
Is there some way to wrap that all up in a target that I can pass
straight to target_link_libraries()?
Or is my only option to create a variable that expands to those
compiler flags?
/M
[1]: https://code.google.com/p/googletest/
--
Magnus Therning OpenPG
is absolute and unaffected by the use of
CMAKE_USE_RELATIVE_PATHS.
I think I'll just have to give up on the idea and dig in my heels in
preparation for the inevitable discussion/complaint when introducing
CMake ;)
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org
that changes made to the solution+projects
don't end up in the CMakeLists.txt automatically. At this point in
time that isn't a big concern for us though.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
able to actually take it for a proper spin at the
moment, but hopefully you don't find my email a complete waste of bits
:)
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.or
Oups, this was due to my own ignorance. I really shouldn't set
CMAKE_SYSTEM_NAME to "Linux" when cross-compiling for an ARM system
with an RTOS :) Sorry for the noise.
/M
On Tue, Mar 19, 2013 at 10:44 AM, Magnus Therning wrote:
> I'm using CMake (2.8.10.2) in an embedde
they don't seem remove the flag on the *compiler
check*. I found an old issue that seems related,
http://www.cmake.org/Bug/view.php?id=9985, it's been closed for years.
Is there some way to remove the flag on compiler checks, or is my only
option to disable compiler checks alltogether?
/M
-
On Mon, Mar 11, 2013 at 8:49 PM, Alexander Neundorf
wrote:
> On Monday 11 March 2013, Magnus Therning wrote:
>> In the project I work on we have tools that generate quite a few
>> header files, but they are all generated with names matching *.inc.
>> I've added them all
tell CMAKE that *.inc files are headers and thus
should go into the headers folders in Eclipse projects?
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
--
ch RCs will be out really soon now. This has
> an additional change which has to do with this.
Ah, I'll definitely have to try that trick.
Another, but related question, when using the Eclipse+Ninja generator
I end up with an awful lot of Ninja-related files in the top level of
the Eclipse project
case *.c and *.cpp)
appear under virtual source folders, there are no header files under
the virtual header folders. (I can provide screenshots tomorrow, if
needed). Adding headers to the sources of apps/libraries has no
effect.
/M
--
Magnus Therning OpenPGP: 0xAB
oodness by far outweighs the trouble of upgrading ;)
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
--
Powered by www.kitware.com
Visit other Kitware open-sour
hen manipulate the includes from there.
Good... well, not that good, but at least I haven't missed anything
when looking for the answer myself ;)
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe
per-target include dirs that work in both these
versions?
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
--
Powered by www.kitware.com
Visit other Kitware open-source p
ned to add full support for slightly esoteric languages
and tool chains like OCaml.
So I've decided that I won't spend more time on OCaml for CMake. Feel free to
take the code and do what you want with it :-)
/M
[1] http://github.com/magthe/cmake-ocaml
--
Magnus Therning
full filename, first extract the
filename-extension (see get_filename_component()) and then add '.o' to that.
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twit
On Fri, Aug 6, 2010 at 20:18, Ryan Pavlik wrote:
> On 8/6/10 1:12 PM, Magnus Therning wrote:
>>
>> I was trying to put something like this into a CMake file:
>>
>> add_custom_command( ...
>> COMMAND ...
>> COMMAND ([[ -f foo ]] || ln -sf foo bar); t
I was trying to put something like this into a CMake file:
add_custom_command( ...
COMMAND ...
COMMAND ([[ -f foo ]] || ln -sf foo bar); true
)
But CMake won't have it. Skipping the sub-shell is all right with CMake:
add_custom_command( ...
COMMAND ...
COMMAND [[ -f foo ]] |
On 05/08/10 20:25, Alexander Neundorf wrote:
> On Thursday 05 August 2010, Magnus Therning wrote:
>> On Thu, Aug 5, 2010 at 10:39, Eric Noulard
>> wrote:
> ...
>>> What is your usage pattern?
>>
>> We ship most of our sources as source RPMs since most
On Thu, Aug 5, 2010 at 10:39, Eric Noulard wrote:
> 2010/8/5 Magnus Therning :
>> I'm currently using CPack to build binary RPMs, is there a way to also
>> generate a source RPM?
>
> Not yet...with CPackRPM.
>
> Building a source RPM with CMake/CPack is not as
I'm currently using CPack to build binary RPMs, is there a way to also
generate a source RPM?
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: m
On Wed, Jun 23, 2010 at 15:41, Eric Noulard wrote:
> 2010/6/23 Magnus Therning :
[...]
>> - The variable CMAKE_INSTALL_PREFIX is not used at all during RPM
>> building. CMAKE_INSTALL_PREFIX is /usr/local, but files get put into
>> /usr in the RPM. Is this a bug?
>
gs end up, but I must be wrong.
Is this a bug?
- The variable CMAKE_INSTALL_PREFIX is not used at all during RPM
building. CMAKE_INSTALL_PREFIX is /usr/local, but files get put into
/usr in the RPM. Is this a bug?
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
mag
I don't think
> there's a way to do so currently. IMHO this would be a good feature-request
> in the bug tracker.
Yes, indeed :-) And how disappointing that CMake doesn't support it already :-(
I created http://public.kitware.com/Bug/view.php?id=10862
Please add clarifying
ed. (I have yet to find out exactly *how* I can determine that
foo already is built, but that sounds like it shouldn't be too difficult.)
4. Call to 'make' (automatic)
Now the Makefile for bar contains the correct dependency information and
the build can continue.
H
the dependency generation to compile time (i.e. when calling `make`)
then I'd be very glad to hear it. Or even better, be pointed to an
example of how to achieve that.
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning
nd in this case the build of foo just
happened before bar, and there was no attempt at automatic generation of
dependencies at all.
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|
On 14/05/10 22:28, Michael Hertling wrote:
> On 05/14/2010 08:24 AM, Magnus Therning wrote:
[...]
>> Thanks for this analysis, it makes the problem a lot clearer to me. One
>> thing it doesn't clarify is how ADD_CUSTOM_COMMAND( TARGET ... POST_BUILD )
>&
On 14/05/10 01:14, Michael Hertling wrote:
> On 05/13/2010 10:43 AM, Magnus Therning wrote:
[...]
>> It's not ideal.
>>
>> I'm writing some CMake scripts to ease the use of OCaml with CMake. There
>> are
>> basically two macros at this point:
>>
&
On Thu, May 13, 2010 at 07:46, Michael Hertling wrote:
> On 05/13/2010 07:36 AM, Magnus Therning wrote:
>> On 13/05/10 02:31, Michael Hertling wrote:
>>> On 05/11/2010 10:51 AM, Magnus Therning wrote:
>>>> I'm still having problems with this.
>>>>
On 13/05/10 02:31, Michael Hertling wrote:
> On 05/11/2010 10:51 AM, Magnus Therning wrote:
>> I'm still having problems with this.
>>
>> I put together this:
>>
>> project( test-post-build NONE )
>> cmake_minimum_required( VERSION 2.8 )
>
KE_CURRENT_BINARY_DIR}
> VERBATIM
> )
Yes, I learned this the hard way too. Basically it seems that an argument in
ticks ("") will be passed in as a single argument (handy when arguments
contain spaces). That means that the equivalent shell command line was
% getrate
On Mon, May 10, 2010 at 17:28, Tyler Roscoe wrote:
> Let's keep this on the list in case it helps someone else.
>
> On Fri, May 07, 2010 at 10:27:16PM +0100, Magnus Therning wrote:
>> On 07/05/10 17:24, Tyler Roscoe wrote:
>> > On Fri, May 07, 2010 at 04:41:23PM
On Tue, Apr 27, 2010 at 15:50, Tyler Roscoe wrote:
> On Tue, Apr 27, 2010 at 02:47:18PM +0100, Magnus Therning wrote:
>> Except of course that it will take away one of the things I *really*
>> want, which is that all unit tests are run every time I compile.
>
> We run our uni
On Mon, Apr 26, 2010 at 20:56, Alexander Neundorf
wrote:
> On Friday 23 April 2010, Magnus Therning wrote:
>> 2010/4/23 Adolfo Rodríguez Tsouroukdissian
> :
>> > On Fri, Apr 23, 2010 at 5:56 PM, Magnus Therning
>> >
>> > wrote:
>> >> On Fri, Apr
What is needed to make it possible to write
project( camlzip MyLanguage )
and then have all the standard macros, add_libary() etc, do the correct thing
for MyLanguage?
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus
2010/4/23 Adolfo Rodríguez Tsouroukdissian :
>
>
> On Fri, Apr 23, 2010 at 5:56 PM, Magnus Therning
> wrote:
>>
>> On Fri, Apr 23, 2010 at 16:35, Tyler Roscoe wrote:
>> > On Fri, Apr 23, 2010 at 04:24:06PM +0100, Magnus Therning wrote:
>> >> A project
On Fri, Apr 23, 2010 at 16:35, Tyler Roscoe wrote:
> On Fri, Apr 23, 2010 at 04:24:06PM +0100, Magnus Therning wrote:
>> A project that I'm currently trying to convert over to CMake has
>> several unit tests written as standalone executables. Are there any
>> examples
A project that I'm currently trying to convert over to CMake has
several unit tests written as standalone executables. Are there any
examples around for integrating the running of such tests as part of
the build in CMake?
/M
--
Magnus Therning(OpenPGP: 0xAB4
On Fri, Apr 23, 2010 at 14:31, Eric Noulard wrote:
> 2010/4/23 Magnus Therning :
>> Is there a target for 'install' that I can add dependencies to by
>> using add_dependencies()?
>
> This is currently unsupported.
>
> There is a feature request for that:
>
Is there a target for 'install' that I can add dependencies to by
using add_dependencies()?
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitt
command in the same
directory.
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe
___
Powered by www.kitware.com
ago but no answer.
I'm not quite sure I understand what you are trying to do. AFAIU your
goal is to do the following:
- compile every C++ file in the directory
- link the resulting object files into a library
Is that correct?
/M
--
Magnus Therning(OpenPGP: 0xAB4D
uld be a way to
solve your problem here?
/M
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．org Jabber: magnus＠therning．org
http://therning.org/magnus identi.ca|twitter: magthe
___
Powered by www.kitware.com
On Mon, Apr 19, 2010 at 11:36, Remy Chibois wrote:
>
> On Apr 19, 2010, at 12:16 PM, Magnus Therning wrote:
>
>> It's some times useful to do an install rooted not at '/' but at some
>> arbitrary location. Is there some way of doing this with the
It's some times useful to do an install rooted not at '/' but at some
arbitrary location. Is there some way of doing this with the GNU
makefiles generated by cmake?
Something like auto*'s 'make install DESTDIR=/where/I/want/it'?
/M
--
Magnus Therning
ear that I'd *really* want to avoid having to write any macros
myself. Using macros copied from some other project would be much
better ;-)
/M
[1]: http://www.mail-archive.com/cmake@cmake.org/msg26809.html
--
Magnus Therning(OpenPGP: 0xAB4DFBA4)
magnus＠therning．or
87 matches
Mail list logo
