[mapguide-users] MySQL FDO and Fedora 4

Sat Nov 11 04:23:34 EST 2006

Hi Tom,

So, does MapGuide need to be compiled against the same revision of FDO that it runs with?  I've often wondered if I need to recompile FDO every time I recompile MapGuide just to keep them in sync.  I guess if the interface is stable I may not need to keep up with FDO?  

Jason

________________________________

From: Tom Fukushima
Sent: Fri 2006-11-10 9:40 PM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] MySQL FDO and Fedora 4

Hi Andy,

Yes, it's a time consuming process. It used to take much longer to compile until Trevor found a way
to speed things up.

I think that what you will find is that FDOCore got compiled, but not the providers.  If you look in 
/usr/local/fdo-3.2.0/lib you should see some libSDF*.* files for the SDF provider.  If they are not there
they were not compiled.  In this case check the directory structure of your fdocore directory: there 
needs to be a fdocore/Providers/SDF directory with all of the SDF source (the subdirectories of SDF
are Docs, Inc, Src and TestData). Similarly for SHP and MySQL. You will only have to recompile 
FDOCore (not Oem or mapGuide) in order to get things to work.

To uninstall: you don't have to delete what you have done so far.  FDO3.2 is compiled to a different directory 
than FDO3.1 so it can be left as is.  MapGuide Open Source (trunk) is compiled to the same place 
as 1.0.x so you should rename the /usr/local/mapguideopensource directory to something else 
before installing 1.0.2.  (Seems a shame to lose all your work in case you want to pick it up again.)
But yes, if you really want to, I think that deleting the two directories will effectively uninstall.

Tom

	-----Original Message----- 
	From: Andy Morsell [mailto:amorsell at spatialgis.com] 
	Sent: Fri 2006/11/10 20:12 
	To: users at mapguide.osgeo.org 
	Cc: 
	Subject: RE: [mapguide-users] MySQL FDO and Fedora 4

	Wow, this is a time consuming process.  I finally got everything to make and install seemingly fine.  I can access the mapagent test page and all seems well.  However, whenever trying to author SDF based layers or accessing existing ones, I get an FDO error:

	An exception occurred in FDO component.
	CLNT_8_UNABLE_TO_LOAD_LIBRARY
	Exception occurred in method MgFdoConnectionManager.Open at line 201 in file FdoConnectionManager.cpp

	I went back and reran the ./configure stage with the --with-fdo-include and --with-fdo-lib configuration options pointing to the /usr/local/fdo-3.2.0/ directories.  That didn't help.

	If I do a mapagent GetFeatureProviders, I get:

	<?xml version="1.0" encoding="UTF-8" standalone="no" ?> 
	- <http://192.168.1.104:8008/mapguide/mapagent/mapagent.fcgi?OPERATION=GETFEATUREPROVIDERS&VERSION=1.0.0&LOCALE=en#>  <FeatureProviderRegistry>
	- <http://192.168.1.104:8008/mapguide/mapagent/mapagent.fcgi?OPERATION=GETFEATUREPROVIDERS&VERSION=1.0.0&LOCALE=en#>  <FeatureProvider>
	  <Name>OSGeo.SHP.3.2</Name> 
	  <DisplayName>OSGeo FDO Provider for SHP</DisplayName> 
	  <Description>Read/write access to spatial and attribute data in an ESRI SHP file.</Description> 
	  <Version>3.2.0.0</Version> 
	  <FeatureDataObjectsVersion>3.2.0.0</FeatureDataObjectsVersion> 
	  <ConnectionProperties /> 
	  </FeatureProvider>
	- <http://192.168.1.104:8008/mapguide/mapagent/mapagent.fcgi?OPERATION=GETFEATUREPROVIDERS&VERSION=1.0.0&LOCALE=en#>  <FeatureProvider>
	  <Name>OSGeo.SDF.3.2</Name> 
	  <DisplayName>OSGeo FDO Provider for SDF</DisplayName> 
	  <Description>Read/write access to Autodesk spatial database format, a file-based personal geodatabase that supports multiple features/attributes, spatial indexing, and file-locking.</Description> 
	  <Version>3.2.0.0</Version> 
	  <FeatureDataObjectsVersion>3.2.0.0</FeatureDataObjectsVersion> 
	  <ConnectionProperties /> 
	  </FeatureProvider>
	  </FeatureProviderRegistry>

	This is also a little odd since I built FDO with all of the other providers in addition to SHP and SDF.

	I'm thinking that I should have just lived with the existing MapGuideOpenSource 1.0.2 and FDO 3.1 binaries instead.  All of this was done simply to try to get MySQL support under Linux........... If I do decide to do this, is uninstalling as simple as deleting the mapguideopensource and fdo-3.2.0 directories?

	Andy 

________________________________

	From: Tom Fukushima [mailto:tom.fukushima at autodesk.com] 
	Sent: Friday, November 10, 2006 8:07 AM
	To: users at mapguide.osgeo.org; users at mapguide.osgeo.org
	Subject: RE: [mapguide-users] MySQL FDO and Fedora 4

	Hi Andy,

	This is an error in the build script.  I have updated the wiki page with instructions on how to get around the error.  Also, when I tried the build_oem.sh command again today, I found that cppunit was not building anymore; I've also added instructions to fix that.

	I'm compiling the latest source now.

	Hopefully that's it
	Tom

	Here is what I added to the wiki page to address this:

	There is a error that will occur the first time this is run. You will need to fix the Svc_Conf_l.cpp file using the following commands: 

	pushd Oem/ACE/ACE_wrappers/ace 

	rm Svc_Conf_l.cpp 

	svn update 

	popd 

	./build_oem.sh 

	Also if you get an error building CppUnit. Try the following: 

	pushd Oem/CppUnit-1.9.14 

	rm aclocal.m4 

	popd 

	./build_oem.sh 

		-----Original Message----- 
		From: Andy Morsell [mailto:amorsell at spatialgis.com] 
		Sent: Fri 2006/11/10 0:26 
		To: users at mapguide.osgeo.org 
		Cc: 
		Subject: RE: [mapguide-users] MySQL FDO and Fedora 4

		Hi Tom,
		I ran through the process today and tonight and ran into a problem when running the mapguide build_oem.sh script.  I get the below errors related to ACE.  I did go through the process of installing GCC 4.0.2 and that is what both GCC --version and G++ --version shows.  Any ideas would be appreciated at this point.  Thank you.

		[root at localhost <mailto:root at localhost>  mapguide]# ./build_oem.sh MapGuide Open Source build script for OEM components OEM Build Initialization ............................ Oem Libraries will be installed at: /usr/local/mapguideopensource /src/mgos/mapguide/Oem /src/mgos/mapguide ace: Initialization...........................
		ace: Configure /Build...........................
		/src/mgos/mapguide/Oem/ACE/ACE_wrappers /src/mgos/mapguide/Oem /src/mgos/mapguide
		/src/mgos/mapguide/Oem/ACE/ACE_wrappers/ace /src/mgos/mapguide/Oem/ACE/ACE_wrappers /src/mgos/mapguide/Oem /src/mgos/mapguide
		make[1]: Entering directory `/src/mgos/mapguide/Oem/ACE/ACE_wrappers/ace'
		 Makefile: /src/mgos/mapguide/Oem/ACE/ACE_wrappers/ace/Makefile.ace
		 g++ -W -Wall -Wpointer-arith -pipe -O3 -g -fno-implicit-templates   -D_REENTRANT -DACE_HAS_AIO_CALLS -D_GNU_SOURCE -DACE_HAS_EXPLICIT_TEMPLATE_INSTANTIATION   -I/src/mgos/mapguide/Oem/ACE/ACE_wrappers -DACE_HAS_EXCEPTIONS -D__ACE_INLINE__ -DACE_BUILD_DLL -DACE_OS_BUILD_DLL  -c -fPIC -o .shobj/Svc_Conf_l.o Svc_Conf_l.cpp
		Svc_Conf_l.cpp:45:1: error: unterminated #if Svc_Conf_l.cpp:207: warning: 'ace_yy_current_buffer' defined but not used
		Svc_Conf_l.cpp:217: warning: 'ace_yy_hold_char' defined but not used
		Svc_Conf_l.cpp:219: warning: 'ace_yy_n_chars' defined but not used
		Svc_Conf_l.cpp:225: warning: 'ace_yy_c_buf_p' defined but not used
		Svc_Conf_l.cpp:226: warning: 'ace_yy_init' defined but not used
		Svc_Conf_l.cpp:227: warning: 'ace_yy_start' defined but not used
		Svc_Conf_l.cpp:232: warning: 'ace_yy_did_buffer_switch_on_eof' defined but not used
		Svc_Conf_l.cpp:248: warning: 'void* ace_yy_flex_alloc(ace_yy_size_t)' declared 'static' but never defined
		Svc_Conf_l.cpp:249: warning: 'void* ace_yy_flex_realloc(void*, ace_yy_size_t)' declared 'static' but never defined
		Svc_Conf_l.cpp:250: warning: 'void ace_yy_flex_free(void*)' declared 'static' but never definedmake[1]: *** [.shobj/Svc_Conf_l.o] Error 1
		make[1]: Leaving directory `/src/mgos/mapguide/Oem/ACE/ACE_wrappers/ace'
		make: *** [all] Error 2
		ACE 5.4: Error build failed (0).................
		[root at localhost mapguide]#

		Andy 
________________________________

		From: Tom Fukushima [mailto:tom.fukushima at autodesk.com] 
		Sent: Thursday, November 09, 2006 9:24 AM
		To: users at mapguide.osgeo.org
		Subject: RE: [mapguide-users] MySQL FDO and Fedora 4

		Hi Andy,

		There is no source provided for the 3.1 MySQL provider.  It is part of the 3.2 source (as you have noticed). If you want to build from the latest source, I put some step by step instructions for building the latest MapGuide source on Fedora Core 4 at http://wiki.osgeo.org/index.php/Building_MapGuide_on_Fedora_Core_4 <http://wiki.osgeo.org/index.php/Building_MapGuide_on_Fedora_Core_4> . I went through this process about a month ago, so I think the steps should be good, but I probably missed something. Of course, feel free to correct, update, reformat, etc. any information on that page.

		Tom

________________________________

		From: Andy Morsell [mailto:amorsell at spatialgis.com] 
		Sent: Wednesday, November 08, 2006 7:11 PM
		To: users at mapguide.osgeo.org
		Subject: [mapguide-users] MySQL FDO and Fedora 4

		I am trying to get all things MapGuide Open up and running on a Linux Fedora 4 install.  One of the requirements is to use MySQL.  When doing the install, I am a little baffled about the FDO build requirements so I'm hoping somebody can shed some light.  The MapGuide Open Source "Building and Configuring on Linux" document says that FDO 3.0 must be built on the server before building MapGuide Server and the Web Extensions.

		So, this leads me to the FDO project where the current Linux FDO tarball only contains the SDF and SHP providers.  The version of FDO is 3.1.  Since I need the MySQL provider, I find that I need to checkout the source from SVN, but SVN appears to only contain FDO 3.2 version source files.  Also, the FDO build PDF file indicates that there should be tar files for the other providers, but the referenced URL only has the above mentioned 3.1 and 3.0 tars.

		Should I build FDO from version 3.2 or not?  Doesn't MGOS 1.0.2 use FDO 3.1 or is that just what comes in the bundled Windows install? Will FDO 3.2 work fine with MGOS if it's manually built?

		Any other hints on the steps to take would be greatly appreciated. 

		Thanks very much. 

		Andy 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 21148 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapguide-users/attachments/20061111/09ef68ba/attachment.bin