On 04 Feb 2015, at 21:25, Peter Stuge <pe...@stuge.se> wrote: >> (and I have a custom pkg-config to detect them), > > Why? Why not do as the manual describes and use PKG_CONFIG_LIBDIR?
On 04 Feb 2015, at 23:58, Andreas Fritiofson <andreas.fritiof...@gmail.com> wrote: > Please also see contrib/cross-build.sh that for the intricacies of cross > building with pkg-config. the script contrib/cross-build.sh also does exactly what I said, define a custom pkg-config for cross builds. the use of various environment variables is debatable, depending on application specifics. and my scripts do much more than your schematic script, actually do everything, download source packages, unpack archives, apply patches, clone repositories, compile all libraries, compile openocd, copy license files, and finally pack the result as a setup/install/archive. so, apart from some misunderstandings related to configure options and to PKG_CONFIG_LIBDIR vs PKG_CONFIG_DIR, if you want to study how production scripts should look like, you can take a look at the build scripts in https://sourceforge.net/p/gnuarmeclipse/openocd/ci/gnuarmeclipse/tree/gnuarmeclipse/scripts/ --- I'll check the difference between PKG_CONFIG_LIBDIR and PKG_CONFIG_DIR and come back to you with the result. regards, Liviu ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
