[Proj] WG: VB Net wrapper Proj.4
support at mnspoint.com
support at mnspoint.com
Tue Aug 8 22:19:04 PDT 2017
Hello,
ok .. this looks like a general library problem. The most common reason
for library problems with MSVC is that you are mixing different kind of
libraries and the compiler or linker gets confused. Out of my head ..
make sure ALL parts of the package use same kind of settings ... meaning
that for example ALL libraries are either debug or release .. and that
all links are either static or dll .. and also make sure that all parts
have similar compiler settings etc. etc -- there is much information
about this problem somewhere in MS help files .. just use some good
keywords and searches -- what ever the MSVC compiler / linker settings
are so confusing that it generates that error. This is rather usual
error when compiling with Visual Studio and there are several libraries
that are built with different switches..
Janne.
------------------------------
stevejking kirjoitti 2017-08-09 00:21:
> RĂ¼esch Thomas wrote
>> Hi Bas
>> Thank you for the fast answer.
>> I got the file, which uses proj 4.4.6. with 32Bit
>> Is the a newer Version of the wrapper dll or one with 64 bit support?
>>
>> Best regards
>> Thomas
>
> After a bit of Googling, I've updated and compiled Eric's VB api
> wrapper
> against the current Proj 4.9.3. But strange the dll no longer seems to
> need
> Proj.dll, so maybe I did something wrong? The files are here:
> https://1drv.ms/f/s!AvBQ7Pt73oO6ghpCVRs1YmTNyVd_
>
> 64 and 32 bit. I've only tested the 32bit dll.
>
> Regards
> Steve
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/WG-VB-Net-wrapper-Proj-4-tp5320211p5330866.html
> Sent from the PROJ.4 mailing list archive at Nabble.com.
> _______________________________________________
> Proj mailing list
> Proj at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/proj
More information about the Proj
mailing list