FDO SDK Questions

[André de Brito]

Hello.

I've been reading most of the documentation available on the FDO website and I have a few questions that I would like to see answered please.

First, I would like to know if, in order to use the FDO SDK for Linux, do I need to build/compile the FDO source? I only want to integrate and use FDO on my code, so I think I should only need to import the libraries included in the SDK package.

Second, I would like to know if anyone has ever tried to use FDO SDK to develop Mac OSX applications or if there's any reason why it should not be possible. From what I read, I think that I should be able to use the Linux SDK to develop a Mac OS application, but I'm not sure.

Last, I would like to get some clarification about the Linux SDK structure. I can see there's a folder containing many header files and another with .so's and .a'a. I'm still a newbie in C++, so I don't really know what to do with those files. I suppose I have to include the header files (something like "#include "include/fdo.h"), but I'm not sure what to do with the libraries (".so" and ".a").

Thanks in advance,

André de Brito

_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users

[Jack Lee-2]

Hi,

The binaries from the SDK are built under RedHat 4. If you version of Linux is compatible with RedHat 4, then you don't need to compile the FDO source.

________________________________
From: [hidden email] [[hidden email]] On Behalf Of André de Brito [[hidden email]]
Sent: Thursday, January 22, 2009 11:17 AM
To: [hidden email]
Subject: [fdo-users] FDO SDK Questions

Hello.

I've been reading most of the documentation available on the FDO website and I have a few questions that I would like to see answered please.

First, I would like to know if, in order to use the FDO SDK for Linux, do I need to build/compile the FDO source? I only want to integrate and use FDO on my code, so I think I should only need to import the libraries included in the SDK package.

Second, I would like to know if anyone has ever tried to use FDO SDK to develop Mac OSX applications or if there's any reason why it should not be possible. From what I read, I think that I should be able to use the Linux SDK to develop a Mac OS application, but I'm not sure.

Last, I would like to get some clarification about the Linux SDK structure. I can see there's a folder containing many header files and another with .so's and .a'a. I'm still a newbie in C++, so I don't really know what to do with those files. I suppose I have to include the header files (something like "#include "include/fdo.h"), but I'm not sure what to do with the libraries (".so" and ".a").

Thanks in advance,
André de Brito

_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users

[Greg Boone]

Some javascript/style in this post has been disabled (why?)

See inline…

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of André de Brito
Sent: Thursday, January 22, 2009 11:17 AM
To: [hidden email]
Subject: [fdo-users] FDO SDK Questions

 

Hello.

 

I've been reading most of the documentation available on the FDO website and I have a few questions that I would like to see answered please.

 

First, I would like to know if, in order to use the FDO SDK for Linux, do I need to build/compile the FDO source? I only want to integrate and use FDO on my code, so I think I should only need to import the libraries included in the SDK package.

[GB] Yes, this is correct. No need to compile FDO. All you need to incorporate all of the SDK components including .so, .a and .h files. The FDO components should be dropped into /usr/local/fdo-3.4.0/lib/ and that path added to your environment.

 

Second, I would like to know if anyone has ever tried to use FDO SDK to develop Mac OSX applications or if there's any reason why it should not be possible. From what I read, I think that I should be able to use the Linux SDK to develop a Mac OS application, but I'm not sure.

[GB] I have begun the process of compiling FDO on Mac OSX. I have not gotten very far yet but am encouraged by my initial results. However, the build will not compile successfully as currently configured. Some modifications are required. I plan to plug away at this in the next few weeks to see what can be done. Most likely any changed will have to go into a Sandbox and be integrated post 3.4.0.

 

Last, I would like to get some clarification about the Linux SDK structure. I can see there's a folder containing many header files and another with .so's and .a'a. I'm still a newbie in C++, so I don't really know what to do with those files. I suppose I have to include the header files (something like "#include "include/fdo.h"), but I'm not sure what to do with the libraries (".so" and ".a").

 

Thanks in advance,

André de Brito

 

_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users

[Greg Boone]

Some javascript/style in this post has been disabled (why?)

Yes.. As Jack stated, the Linux SDF is built on RH 4. So you Linux build has to be compatible.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Greg Boone
Sent: Thursday, January 22, 2009 11:41 AM
To: FDO Users Mail List
Subject: RE: [fdo-users] FDO SDK Questions

 

See inline…

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of André de Brito
Sent: Thursday, January 22, 2009 11:17 AM
To: [hidden email]
Subject: [fdo-users] FDO SDK Questions

 

Hello.

 

I've been reading most of the documentation available on the FDO website and I have a few questions that I would like to see answered please.

 

First, I would like to know if, in order to use the FDO SDK for Linux, do I need to build/compile the FDO source? I only want to integrate and use FDO on my code, so I think I should only need to import the libraries included in the SDK package.

[GB] Yes, this is correct. No need to compile FDO. All you need to incorporate all of the SDK components including .so, .a and .h files. The FDO components should be dropped into /usr/local/fdo-3.4.0/lib/ and that path added to your environment.

 

Second, I would like to know if anyone has ever tried to use FDO SDK to develop Mac OSX applications or if there's any reason why it should not be possible. From what I read, I think that I should be able to use the Linux SDK to develop a Mac OS application, but I'm not sure.

[GB] I have begun the process of compiling FDO on Mac OSX. I have not gotten very far yet but am encouraged by my initial results. However, the build will not compile successfully as currently configured. Some modifications are required. I plan to plug away at this in the next few weeks to see what can be done. Most likely any changed will have to go into a Sandbox and be integrated post 3.4.0.

 

Last, I would like to get some clarification about the Linux SDK structure. I can see there's a folder containing many header files and another with .so's and .a'a. I'm still a newbie in C++, so I don't really know what to do with those files. I suppose I have to include the header files (something like "#include "include/fdo.h"), but I'm not sure what to do with the libraries (".so" and ".a").

 

Thanks in advance,

André de Brito

 

_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users

[André de Brito]

Thanks very much for the information. Looking forward to that Mac OSX build.

André de Brito

_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users