search

pombreda / libkml

Automatically exported from code.google.com/p/libkml
Other
0 stars 0 forks source link

Need sln and vcproj files for VS2008 #47

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

The sln and vcproj files provided are for Visual Studio 2005, and it is 
very difficult to use these with Visual Studio 2008. VS2008 converts them 
automatically, but linking with VS2008 is a problem.

What is the expected output? What do you see instead?

I can't get the example programs to link using VS2008.

What version of the product are you using? On what operating system?

libkml-0.6.1, Visual Studio 2008, Windows XP.

Did you run the unit test suite that comes with the project? Did all tests 
pass?

No. Can't build them.

Please provide any additional information below.

Original issue reported on code.google.com by anthony....@gmail.com on 23 Jan 2009 at 5:39

GoogleCodeExporter commented 9 years ago 
The sln and vcproj files provided are for Visual Studio 2005, and it is 
very difficult to use these with Visual Studio 2008.I hope it will support 
VS2008 
thanks

Original comment by cailu2...@163.com on 12 Jan 2010 at 7:10

GoogleCodeExporter commented 9 years ago 
I'm not sure if this note is up to date or not but BuildingAndInstalling says

"(It is known that Microsoft Visual Studio 2008 does not work with libkml) "

Could anyone clarify it?

Original comment by mloskot on 24 Feb 2010 at 8:25

GoogleCodeExporter commented 9 years ago 
We're erring on the side of caution in the notes. Some have reported that the 
MSVC 
2005 sln/vcproj files we supply work just fine with their 2008; others report 
insurmountable incompatibilities.

Neither I nor my other developer have access to 2008, so we're unable to 
investigate. 
We'd appreciate any help we can get.

Original comment by kml.mash...@gmail.com on 24 Feb 2010 at 8:34

GoogleCodeExporter commented 9 years ago 
I got all the libraries and tests to build.  Besides converting all the 
.vcproj's to VS2008, I also had to rebuild third_party/uriparser-0.7.5.win32 in 
VS2008 to get the tests to run.

Most of the tests pass (except for the time ones, which it looks like the 
module is just not done yet).  

As far as examples, I have 3 building and 4 failing to build.  The reason is 
zlib.  I have not yet figured out what is the deal with minizip.dll (It doesn't 
seem to be a part of a standard zlib build).

The examples that are building:  createkml, csvregionator, parsekml
The examples that will not build: change, prettykml, printstyle, sortplacemarks

Since I'm using libkml to pass KML directly to the Google Earth COM interface, 
I'm happy with what I got.  I'll try to post the solutions/project/dependencies 
here once I clean everything up.

Original comment by aleksey....@gmail.com on 8 Jul 2010 at 7:56

GoogleCodeExporter commented 9 years ago 
I am finding the limit using libkml with the more modern vs8 to be rather 
prohibitive in adopting it an making proper use of kml (we currently have our 
own parser with noteable limits in the areas of network link management 
especially)

Original comment by lanceala...@gmail.com on 13 Jul 2010 at 5:48

GoogleCodeExporter commented 9 years ago 
As promised, I'm posting my VS2008 build files.  It includes the msvc build 
directory with all the projects and solutions, as well as vc9 lib's from the 
third_party directory.  All the tests pass except for the DateTime stuff which 
is not implemented.

Only 3 out of 7 examples build because of the 3rd party libraries.  I could not 
readily figure out how to build zlib in the configuration they are using, but I 
didn't care anyway, so I didn't bother trying any longer.  createkml, 
cvsregionator, and parsekml build and run just fine.

Original comment by aleksey....@gmail.com on 15 Jul 2010 at 2:51

Attachments:

GoogleCodeExporter commented 9 years ago 
Using the most recent download (Feb 2010), the linking for the uriparser in the 
thirdparty directory is inconsistent with the files included in the download. 
this is what causes 4 of the 7 examples to fail to build for me (using VS2008). 
the 4 examples are change, prettykml, printstyle and sortplacemarks. this can 
be fixed by editing the properties of each project to direct it to the correct 
library folder and correct library (the folder listed in the project is 
uriparser-0.7.1.win32, while the actual folder included in the download is 
uriparser-0.7.5.win32 and the libraries called out are uriparser-debug.lib and 
uriparser-release.lib but the actual libraries provided are both uriparser.lib.

Original comment by Jennay...@gmail.com on 18 Aug 2011 at 2:08