As rightly pointed out, the problem was in compiler settings. I had compiled my driver in /MT instead of /MD Now it is working perfectly.
But I faced a problems. I had to compile all the related libraries using /MD too. Luckily I could. But what if I have I cannot get a MD version of a lib? does GDAL give the driver writer the option to do the 'delete' of their driver object themselves (Because he does the 'new' on his heap in GDALRegister()). There can be a function pointer like pfnDeleteDriver in GDALDriver. If it is NULL then GDAL can do the delete. Thank you very very much for your support. On Tue, Nov 23, 2010 at 2:51 AM, Tamas Szekeres <szeker...@gmail.com> wrote: > > > 2010/11/22 Ram prasad <ramprasa...@gmail.com> >> >> Following is repost, because the message appeared garbled in the mailing >> list. >> >> I could not compile my code along with other formats in frmts due to >> my insufficient experience in using nmake projects. >> >> http://www.gdal.org/gdal_drivertut.html gives information on writing a >> driver. >> Is there a document on compiling the driver? I need to be able to >> specify the search path for include files for the compiler and input >> files for the linker. >> > > > If you download the -dev package from http://vbkto.dyndns.org/sdk/ it > should contain all the required libs and headers to compile the plugin. Make > sure to compile with the /MD setting to use the same CRT dependency for the > plugin and the gdal dll. > > Best regards, > > Tamas > > > -- "Love all serve all" - ..::Sri Sathya Sai::.. _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
