You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to build libmpsse trunk (r202) out-of-source. So something like:
cd somedirectory
../../../libmpsse/src/configure --prefix=/local_install_directory
CFLAGS="-I/myotherrootfs" LDFLAGS="-L/myotherrootfs/lib64"
Configure succeeds and generates a makefile but the file names are all relative
to the original source directory.
This looks to come directly from Makefile.in (I'm not super familiar with
autotools at this point):
mpsse.o: support.o
$(CC) $(CFLAGS) $(LDFLAGS) -DLIBFTDI1=$(LIBFTDI1) -c mpsse.c
I've started to modify the Makefile.in to use ${srcdir) etc but I'm wondering
if you would be opposed to switching to cmake. Libftdi uses it for their build
system and I suspect it would make it much easier to handle things like this.
It would also make it easier to detect libftdi, there is a helpful cmake script
that libftdi installs that will retrieve the libraries and include paths.
I could provide the CMakeLists.txt file if that would be helpful as I need to
integrate this into our build system and we try hard to perform out-of-source
builds.
[email protected] if you want to get ahold of me.
Original issue reported on code.google.com by [email protected] on 14 Oct 2013 at 1:14
The text was updated successfully, but these errors were encountered:
I've actually completed the switch on my github account. Check it out here:
https://github.com/chmorgan/libmpsse
And let me know how it works for you. Patches welcome.
Chris
I've updated this cmake_wip branch to include a find_packages() script for
libmpsse, along with an example of how to find libmpsse from your
CMakeLists.txt file.
Original issue reported on code.google.com by
[email protected]
on 14 Oct 2013 at 1:14The text was updated successfully, but these errors were encountered: