Update of /cvsroot/monetdb/pathfinder/NT
In directory sfp-cvsdas-4.v30.ch3.sourceforge.com:/tmp/cvs-serv12985/NT
Modified Files:
Tag: M5XQ
pf_config.h.in
Log Message:
propagated changes of Thursday Apr 08 2010
from the XQFT branch to the M5XQ branch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2010/04/08 - sjoerd: NT/pf_config.h.in,1.12.12.1
propagated changes of Wednesday Mar 31 2010 - Thursday Apr 08 2010
from the development trunk to the XQFT branch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2010/03/31 - stmane: NT/pf_config.h.in,1.13
Made compilation of "testing" (and "java") independent of MonetDB.
This is mainy for Windows, but also on other systems, "testing" can now be
built independently of (and hence before) "MonetDB".
(These changes require a complete rebuild from scratch on Windows.)
1)
Moving files that mimic configure functionality on Windows from "MonetDB" to
"testing"; in detail:
MonetDB/conf/configure.py -> buildtools/conf/configure.py
MonetDB/NT/winrules.msc -> buildtools/conf/winrules.msc
MonetDB/NT/monetdb_winconfig.h -> buildtools/conf/winconfig.h
With winrules.msc & monetdb_winconfig.h no longer distribute in the MonetDB
tarball, this now prohibits compilation on Windows from tarballs. However,
this has never been tested, let alone supported, and most probably did not
work, anyway, as configure.py was never distributed in any tarball.
In fact, now there are only two places (see hereafter) where the location of
the above three files it specified. All three are guarded by compile time
option "NEED_MX" to indicate whether "Mx" is required or not, and hence,
whether we build from CVS sources or tarballs. The location is given for
the former case. For the latter case, we'd "simply" need to ensure that
these three files are included in some (or each) tarball and specify there
location in case we build from tarballs.
buildtools/conf/winrules.msc:
!IFDEF NEED_MX
CONFIGURE_PY = "$(TOPDIR)\..\..\buildtools\conf\configure.py"
WINCONFIG_INCS = "-I$(TOPDIR)\..\..\buildtools\conf"
!ELSE
CONFIGURE_PY = ToBeDefined
WINCONFIG_INCS = ToBeDefined
!ENDIF
*/NT/rules.msc:
!IFDEF NEED_MX
RULESMSC = $(TOPDIR)\..\..\buildtools\conf\winrules.msc
!ELSE
RULESMSC = ToBeDefined
!ENDIF
2)
Replicating the getopt code from
buildtools/Mx/mx_getopt.h & buildtools/Mx/getopt.c
into
testing/src/testing_getopt.{h,c}
--- at least for the time being.
A better solution than replicating source files needs to be found, not only
for testing, but for getopt in general, as we now have already 4 copies of
some (different) getopt implementations in our code base.
3)
Making the remaining code aware of the above changes.
buildtools/doc/windowsbuild.rst,
*/NT/rules.msc:
new location of "winrules.msc"
*/NT/*_config.h.in:
renamed "monetdb_winconfig.h" into "winconfig.h"
MonetDB/NT/Makefile:
removed "winrules.msc" & "monetdb_winconfig.h"
testing/configure.ag,
testing/MonetDB-testing.spec,
testing/vertoo.config,
testing/vertoo.data,
testing/NT/rules.msc:
removed MonetDB build requirement
testing/src/Makefile.ag,
testing/src/Mdiff.c:
use local "testing_getopt.{h,c}"
testing/conf/monetdb-testing-config.in,
testing/conf/monetdb-testing-config.bat.in:
removed conditional "HAVE_MONETDB"
clients/conf/Tests/monetdb-testing-conds.stable.out.*:
updated stable output accordingly
TestTools/*:
build "testing" before "MonetDB"
monetweb/Development/TestWeb//*:
"testing" before "MonetDB"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Index: pf_config.h.in
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/NT/pf_config.h.in,v
retrieving revision 1.12
retrieving revision 1.12.2.1
diff -u -d -r1.12 -r1.12.2.1
--- pf_config.h.in 26 Mar 2009 09:05:47 -0000 1.12
+++ pf_config.h.in 8 Apr 2010 11:32:36 -0000 1.12.2.1
@@ -20,7 +20,7 @@
/* Manual config.h. needed for win32 . */
-#include <monetdb_winconfig.h>
+#include <winconfig.h>
#define VERSION "@VERSION@"
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Monetdb-pf-checkins mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-pf-checkins
