[gdal-dev] Instructions for a new writing driver?

[Laurențiu Nicola]

PS: Geoconcept might be a better example than AAIGrid, since it's a vector driver.

On Thu, Jul 6, 2023, at 16:08, Laurențiu Nicola via gdal-dev wrote:
> Hi,
> 
> I think some existing drivers already contain some C files, AIGRID for example. Others have a sdk subdirectory with library code in there. I don't think including your code as C will be a problem.
> 
> On the other hand, offering a C API for new drivers might be an interesting idea. Using C++ makes writing drivers in other languages a bit more complicated. But I know this wouldn't be trivial, since GDAL uses inheritance.
> 
> Laurentiu
> 
> On Thu, Jul 6, 2023, at 16:01, Abel Pau wrote:
>> Hi again.
>> I finally did that and I am happy.
>>  
>> It would be helpful for us to be able to use our C functions to read and write some parts of our format instead of passing all of them to C++.
>> I’d like doing that but it’s not possible for the moment convert all our code to C++.
>>  
>> My proposal is use a ogrmiramondatasource.cpp, a ogrmiramondriver.cpp and a ogrmiramonlayer.cpp as all of the projects that are created and add our files from C as necessary.
>> The main goal is adding only the necessary ones.
>>  
>> The question: Is this possible? Can I simply add C files and use that functions from C++ files? Or do GDAL prefer doing it in another way?
>> Sorry if it is written somewhere else but I couldn’t find it.
>>  
>> Thanks again for your kind help.
> 
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20230706/121edfdf/attachment.htm>