Andreas Pakulat wrote:
This is Ok for building an executable, but linking a static lib into a
shared lib is completely unportable and not supported on all operating
systems that cmake supports. Thats why its not done.
Huh? I'm not aware of that as a limitation - you *do* need the objects
in
Bill Hoffman wrote:
James Mansion wrote:
So, C++ is the language we picked/like. You are welcome to contribute
one in C++. Imagine if you could develop generators (I assume that is
what you mean by emitters) in any language! You wouldn't even be able
to share them.
Bill, I like C++ as
Bill Hoffman wrote:
So what exactly about the CMake language gives you this feel?
That would be:
1) the syntax
and
2) the modularity constructs
I know its 'only' scripting to manage declarations into the engine.
Its a shame you can't write emitters except in C++ but that certainly
wouldn't
Sebastien BARRE wrote:
Again: *deal*.
February 29th, 2010 *precisely*.
Special CMake/Lua day, the 29th.
That will indeed be a very special day.
Shame really. I like Lua, and I find that the CMake script language
seems designed to make COBOL coders feel they don't actually
have the worst job in
Ken Martin wrote:
other's variables out of the box. But with the Modules directory we either
have to have a copy of each module for every possible scripting language, on
the fly converters between any two scripting languages, or something like
that to make it work. Trying to figure out how to man
Gonzalo Garramuño wrote:
In summary, once you use git, if you are like me, you'll realize that
you've been doing source version control wrong all these years *sigh*.
Does git work on Win32?
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org
I think you need a dependency declaration too don't you?
I've seen VStudio 2k3 build out of order without.
># App/CMakeLists.txt
>ADD_EXECUTABLE(myexe ...)
>TARGET_LINK_LIBRARIES(myexe mylib)
It seems actually a little more complicated in practice
because you probably want mylib's headers (possi
> Do you know if they work on Borland, MinGW, and cygwin as well as VS?
I don't see why not. A .lib file isn't very sophisticated, why
wouldn't they? I can't test any of those at the moment because the
Mingw I have is the modified one from U++ that doesn't work with
CMake, unfortunately.
__
>
http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_lib
raries.3F
The FAQ is misleading - they DO make sense for (all) non-UNIX linkers. What
non-UNIX linkers do not have an equivalence to an archive?
There is no reason why I cannot compile a load of objects with DLL
compi
>Are you trying to link object files compiled without -fPIC into a shared
>library? That would never work; -fPIC is required for all objects in
shared
>libraries.
I'm guessing so - I want to do it too! Or rather, be able
to make a static library containing objects that can be linked
to create a
>Yes a GPL'd app can use a Cmake build system. The cdrecord issue is more
>about how one person is out of touch with the rest of the world on what
>the GPL says. Pay no attention to that person.
This is bull. Paying no attention to what Joerg says is a mistake.
You might disagree with the focus o
Nope, pilot error. :-( The joys of using a touchpad on a train, it seems I
clicked above the line I expected. This was apparent when I reran
CMakeSetup after blowing away the generated files.
Sorry about that.
Maybe an idea for CMakeSetup to put the selected toolset on the dialog
rather promine
I fired up cmakesetup to create nmake files and it whinged that it can't
find gcc.exe.
Which is fair enough because my msys shell prompts have that but my VStudio
ones don't.
Surely if someone has nmake then they have a Microfoft compiler, and if they
have gcc then they are more likely to use the
>Please give specific examples of this, these are bugs. For the most part
the properties
>should match the flags used.
Most recently I noticed with 'defines' and I think include
paths. But definitely the project relationships don't seem
set up. I'll try to distill something.
___
> MinGW / MSYS and Cygwin are fine
also. Windows != Visual Studio. :-)
In
20-something years working (mostly in investment backs) on systems
with
Win32
and UNIX deployment, I've *never* seen a team deploy C or C++
on
Win32
with gcc.
VisualStudio is number 1 by an enormous margin. L
Do you actually need to add -L?
I think if you have:
link a.obj c:\foo bar.lib
(and c:\foo is a directory)
then it will look for bar.lib in c:\foo.
Haven't tried myself, but recently I recall seeing the thread started here:
http://www.digitalmars.com/drn-bin/wwwnews?c%2B%2B.command-line/639
a
>For those that run Windows (and don't have the unixtools installed) the
>preferred interface is a GUI anyway.
I don't think that's a good assumption. Windows has a command interpreter
(and in my experience people erroneously believe CMD.EXE is as limited as
COMMAND.COM without having looked at
I'd like to create a library from a mix of
assembler and C files.
I'm reading the book to try to determine how
to achieve this. There seems to be perhaps two
possible approaches.
(Initially this is for Win32, and I have files for NASM
and MASM with extensions .nasm and .masm)
1) define new lang
>When I change a couple of header files I suddenly see it reconfiguring for
>no apparent reason.
Is the generated makefile thinking that there is a change in
CMakeLists.txt somewhere? Surely cmake is actually out of the
picture unless you tell it to rebuild the makefiles?
>Its when I type 'make
Has anyone managed to build OpenSSL with CMake?
(I'm not looking for FindOpenSSL - I want to build the package itself)
James
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
>There will probably be a way to set the *interface*
>include file search path separately from the
>*implementation* search path. Then when a library is
>linked its interface include file search path can be
>included during compilation of source files using the
>library.
Great - and hopefully no
>Conv. libs are not (officially) supported by cmake. Just
>compile all source files into the resulting library. That's
>what we do for KDE.
Oh, tht's a shame. I was hoping to be able to use a single
structure which would build static or dynamic libs as either
multiple small libraries or one big o
>I.e. there are modules for each library, and these modules
>(should) define a standard set of variables whioch give you
>the required information.
Thanks - but its not what I wanted to hear. :-(
It does load a lot of identical donkey-work onto every dependent
project. In my case, also, its not
(Another stupid noob question, sorry!)
bjam has a handy feature where I can define a build
for a library and specify that a project that uses
the library will automatically get certain settings,
such as an appropriate #include and defines.
I don't seem to be able to do this automatically.
Have I
(Another noob I couldn't find in the book today)
I'm building VS2003 project files OK and my
system gets built, but normally when I set up
VStudio projects I add in the includes and
the documentation text and web files so I can
select them easily for editing.
I find myself missing this in the ge
Is it possible to convince CMake to build a set of convenience libraries and
then a main library?
By convenience library, I mean a (static?) library that contains objects.
Or possibly just a zip file of objects.
Where the target main library is static, the objects are compiled for static
library
26 matches
Mail list logo
