common.mk


# common flags used in openocd build
AM_CFLAGS = $(GCC_WARNINGS)

AM_CPPFLAGS = $(HOST_CPPFLAGS)\
			  -I$(top_srcdir)/src \
			  -I$(top_builddir)/src \
			  -I$(top_srcdir)/src/helper \
			  -DPKGDATADIR=\"$(pkgdatadir)\" \
			  -DBINDIR=\"$(bindir)\"

if INTERNAL_JIMTCL
AM_CPPFLAGS += -I$(top_srcdir)/jimtcl \
			   -I$(top_builddir)/jimtcl
endif
build: add common.mk Rather than specifying common makefile variables move them all to a common.mk. Signed-off-by: Spencer Oliver <ntfreak@users.sourceforge.net> 2010-11-12 11:41:55 +00:00
			`# common flags used in openocd build`
configure: Don't set user variables CFLAGS is a user variable and shouldn't be set in either configure.ac or Makefile.am because that makes it impossible to override compiler flags at configure or make time. AC_SUBST the default warning flags into AM_CFLAGS instead, which is emitted before CFLAGS on the compiler command line. Do the same thing with a mingw-specific flag as well. Change-Id: I6ac3a3c8b7e0abf6f0e60ea239b549d68ea6d370 Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Reviewed-on: http://openocd.zylin.com/3870 Tested-by: jenkins Reviewed-by: Paul Fertser <fercerpav@gmail.com> 2016-11-06 15:49:35 +01:00			`AM_CFLAGS = $(GCC_WARNINGS)`

			`AM_CPPFLAGS = $(HOST_CPPFLAGS)\`
			`-I$(top_srcdir)/src \`
build: add common.mk Rather than specifying common makefile variables move them all to a common.mk. Signed-off-by: Spencer Oliver <ntfreak@users.sourceforge.net> 2010-11-12 11:41:55 +00:00			`-I$(top_builddir)/src \`
jim-nvp is moving from jimtcl to openocd The jim-nvp code is specific to openocd, so it belongs in openocd, not in the core jimtcl. Signed-off-by: Steve Bennett <steveb@workware.net.au> 2011-09-29 16:12:41 +10:00			`-I$(top_srcdir)/src/helper \`
Add -DPKGLIBDIR to AM_CPPFLAGS. This is required so the OpenULINK driver knows the install location of the OpenULINK firmware image. 2011-06-20 19:51:46 +02:00			`-DPKGDATADIR=\"$(pkgdatadir)\" \`
Remove special handling of script search path on Windows On all platforms, search for scripts in $HOME/.openocd ${run_prefix}${pkgdatadir}/site ${run_prefix}${pkgdatadir}/scripts On Windows, set run_prefix to the runtime path of the executable, minus ${bindir}. This is to enable the install dir to be moved anywhere, as long as the structure of the install dir is kept intact. On all other platforms, run_prefix is empty. The script paths can now be adjusted on Windows builds the normal way; by overriding pkgdatadir at build time. For example, to create a Windows package layout of bin/openocd.exe scripts/interface/... scripts/target/... you can do configure --prefix= --enable-... and then make pkgdatadir= DESTDIR=/some/path clean all install Also, remove the unused PKGLIBDIR define. Change-Id: If2c8228fc80c598d763efad21c5f51695ff9b6cf Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Reviewed-on: http://openocd.zylin.com/1796 Tested-by: jenkins Reviewed-by: Jens Bauer <jens@gpio.dk> Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk> 2013-07-27 17:27:01 +02:00			`-DBINDIR=\"$(bindir)\"`
build: add autobuild jimtcl to configure scripts Rather than having to configure/build jimtcl openocd will do this as part of its own build. To use an external jimtcl lib specify disable-internal-jimtcl to the configure step. Signed-off-by: Spencer Oliver <ntfreak@users.sourceforge.net> 2010-11-17 10:26:21 +00:00
			`if INTERNAL_JIMTCL`
			`AM_CPPFLAGS += -I$(top_srcdir)/jimtcl \`
			`-I$(top_builddir)/jimtcl`
			`endif`