Alternative build system (CMake) about libnfc HOT 7 CLOSED

Ok, so it got a bit out of hand. I've added Windows support to the CMake files 
now
and it seems to work quite smooth. Features:

- creates a shared (DLL) library for Windows
- compiles the tools using this shared library
- generates a LIB file which is used to compile against the DLL
- create a NSIS installer right from MSVC

Remarks:
- in order for it to work really smooth the nfc DLL should be added to
WINDOWS\SYSTEM32 (or at least a directory in PATH), but that would require admin
privileges afaik, so current version works as a normal user as well (by placing 
the
DLL together with the example apps)
- at compile time it depends "hard" on WinSCard.Lib provided by MSVC 2008 
Express (I
didn't want to use a separate winscard.lib file)
- it depends on libusb-win32 project, it needs to be installed and uses the 
shared
library from it
- the libnfc.h and bitutils.h needed to be modified (export the functions that 
should
be available in the DLL through the LIB file) 
- some of the example tools (that use getopt) don't compile anymore, but this 
is also
a problem in current SVN

Attached are updated versions of the CMakeLists files.

Hey Fkooman,

Thanks for your help !
I don't usually use CMake stuff, but you say that "it can be
considered a replacement for Autotools." So, I have some questions :
 1) What's benefit with CMake ?
 2) Does it allow cross-compiling ?
 3) Does it work under POSIX platforms or just under Linux ? 
 4) Do it make sense if we provide CMake and Autotools (CMake seems to more fit to
Windows users needs) ?

> 1) What's benefit with CMake ?

No Autotools, no libtool, seems like a benefit to me :) Other than this: it is a
complete system with only 2 configuration files in the entire tree, cross 
platform.
See http://en.wikipedia.org/wiki/Cmake for a more comprehensive list.

Also CPack is nice, as mentioned above you can create a Windows installer right 
from
CMake/Visual Studio. And CMake-gui is interesting as well, you can easily set
configuration parameters there (like enable DEBUG or C99 compiler flags etc).

On Linux you would use "make package" or "make package_source" to create a 
binary /
source package.

> 2) Does it allow cross-compiling ?

Yes, see http://www.cmake.org/Wiki/CMake_Cross_Compiling, I didn't look into 
this yet
in detail. What do you want to cross compile for? 

> 3) Does it work under POSIX platforms or just under Linux ? 

* Linux and other POSIX systems (including AIX, *BSD systems, HP-UX, IRIX/SGI, 
and
Solaris)
* Mac OS X
* Windows 95/98/NT/2000/XP, Windows Vista and MinGW/MSYS

> 4) Do it make sense if we provide CMake and Autotools (CMake seems to more 
fit to
Windows users needs) ?

This makes perfect sense! Choice is good, and this seems like the way to go at 
first,
once all use cases are provided for by CMake it is still possible to throw 
Autotools
out, but not necessary at all. CMake only has 2 .txt files anyway.

I'll attach the latest version of the scripts again, and maybe you could try it 
out
at some point and let me know what you think (add the CMakeLists.txt to the 
project
root and the CMakeListsSRC.txt to the src directory as CMakeLists.txt as well)

$ apt-get install cmake cmake-gui
$ cd /path/to/libnfc-1.2.2/
$ mkdir bin
$ cd bin
$ cmake-gui ..   (or "cmake .." if you don't want to modify parameters)

  < play around with settings, press configure/generate to create Makefile >

$ make 
$ make install DESTDIR=foo  # to install everything under directory foo
$ make package              # to generate binary package
$ make package_source       # to generate source package

Thanks for reply and explanations.

1) I don't care Windows stuff and don't like GUI (which seems always less 
powerfull
than command line) but libnfc care about Windows users, so if it can be more 
handy
for them..

2) I cross-compile to run libnfc on routers using OpenWrt and smartphone 
(Openmoko
FreeRunner) using various distributions (SHR, Hackable:1, OpenWrt). That's why i
introduce Autotools in libnfc.

3) Fine.

4) Great ! Your two files have been commited in r82, but "target" and 
"initiator"
targets have been removed since they are not commited yet (lack of 
documentation).

Many thanks for help !

I've updated the CMake files and fixed a pkg-config file bug at the same time. 
Patch
against current SVN.

Addressed:
- configure option to not compile PC/SC support (defaults to ON)
- fix pkg-config: @PACKAGE@ should not be in libdir line (at least, that is not 
where
autotools actually puts it...)
- sync variables in CMake file with current pkg-config file variables so it 
actually
works...

For Windows, more work is required... (the header files need to be updated). 
Expect
patch later.

Hi Fkooman,

The bug introduced by fixing "Issue 7" in pkg-config file has been fixed in r85.

CMake files have been updated in r86, but please make sure that files doesn't 
have
DOS line endings.

Thanks.