Even Rouault
Even Rouault
The content of the gdal_alg.html pages and other similar API pages is dynamically generated from Doxygen documentation of C/C++ functions. Not everything is convenient in life :-) That's the point...
> Would it be helpful if I put a comment at the top of the `.rst` files along the lines of "the text rendered on this page is automatically generated...
> My workaround is to add -nomd to all my scripts where a privileged user would import files into the db so that ogr_system_tables.metadata is never created in the first...
> Does this change perhaps resolve also that? I believe the test https://github.com/OSGeo/gdal/pull/10004/files#diff-7dbd738af5dc94c81fdbfda0c672f9f3f7a63382b22771fa0a679b8917513ef8R3185 added in PR #10004 should also resolve that case
> * I know you also mentioned setting `--config OGR_PG_ENABLE_METADATA NO` and I see where support for that was added in ... but I can't get this setting to work....
> It doesn't fix the issue well, I did test it successfully locally on UCRT64 config > gdal_pdal.h is included first other heaters will redefine GetObject. no, since we import...
Can you give more details on the components that are installed on your system? I can't reproduce with: ``` $ ~/install-python-3.12.0/bin/python3 -m venv myvenv_py312 $ source myvenv_py312/bin/activate $ python3 -m...
> Are you building module from gdal source tree? (from swig/python) yes
@kloczek How can I reproduce your environment? Ideally, running a sequence of commands in a Docker image with the base distribution you use.
ok, I finally managed to reproduce your error message if I run "python3 -sBm build -w --no-isolation" from the "swig/python" subdirectory of the *source* tree, which is fully expected. This...