Open GoogleCodeExporter opened 9 years ago
Original comment by olof.nae...@gmail.com
on 6 Aug 2008 at 2:37
Original comment by olof.nae...@gmail.com
on 8 Aug 2008 at 8:50
why not generate a .pc for pkg-config and use FindPkgConfig from cmake?
Original comment by ibo...@gmail.com
on 16 Oct 2008 at 11:28
Ok. Here is what I've made in 30 mins :)
The guichan-sdl.pc is a very basic pkg-config file. (You could probably make a
common
guichan.pc that is required by guichan-allegro.pc, guichan-sdl.pc, etc).
With this, you can use guichan-sdl from cmake like this:
pkg_check_modules(GUICHAN_SDL REQUIRED guichan-sdl)
message("GUICHAN_SDL --libs: ${GUICHAN_SDL_LIBRARIES}")
I think this is much more simple than making the real cmake stuff (I'm not a
cmake
expert, but, except the total lack of cmake docs, I love it).
As an added bonus, it is also a more general solution :)
Original comment by ibo...@gmail.com
on 16 Oct 2008 at 12:01
Attachments:
With CMake support I was thinking about making Guichan build with CMake, not
finding
the libraries with CMake. We already have a pc-file for Guichan and Guichan SDL
present in the SVN repository.
The reason I want CMake support is the fact that it will be very easy for
people to
generate their own project files for various of IDE's and environments, like
different versions of Visual Studio. Also, the CMake support is almost in
place. At
least it works fine under Linux.
Original comment by olof.nae...@gmail.com
on 16 Oct 2008 at 1:02
that's good news. i'm hardly waiting for the new release :D
Original comment by ibo...@gmail.com
on 17 Oct 2008 at 10:01
Is there any progress on switching to CMake? It still isn't included in the
0.8.2
source download (only git). I'd like to get some proper support for the
Irrlicht
backend in Guichan and it now builds properly with CMake... If we can include
CMake
then I can probably get the Irrlicht backend packaged up in Debian.
Original comment by aaron.r....@gmail.com
on 9 Dec 2009 at 3:53
Guichan should build properly with CMake by now as far as I know, so I don't
really
see a reason to not include it when making the next package.
Original comment by olof.nae...@gmail.com
on 9 Dec 2009 at 4:36
Let's just remove the autoconf stuff then.
Original comment by b.lindeijer
on 9 Dec 2009 at 4:40
Although I'm not really sure how to make packages with CMake, at the moment
autotools
does the job with make dist. Looks like we need to use something like CPack,
http://www.cmake.org/Wiki/CMake:Packaging_With_CPack.
Original comment by olof.nae...@gmail.com
on 9 Dec 2009 at 4:48
For Tiled Qt, which uses qmake instead of autoconf, I just use git archive.
We'd just
need to verify that everything tracked by git is suitable for distribution, but
that
is usually the case.
See my little make-dist.sh script here:
http://gitorious.org/tiled-qt/mainline/blobs/master/make-dist.sh
Original comment by b.lindeijer
on 9 Dec 2009 at 5:05
Sounds like a good idea to use a similar script!
Original comment by olof.nae...@gmail.com
on 9 Dec 2009 at 9:38
Original issue reported on code.google.com by
olof.nae...@gmail.com
on 16 Jul 2008 at 6:18