Compilation issues for iOS and XCode 15 about libosmscout HOT 5 CLOSED

Hi @vyskocil : Is this fixed with your pull request (and we can close the issue?) or is this a separate issue?

from libosmscout.

Hi @Framstag ! This is a separate issue I discovered after updating the build process that let it compile with current Xcode version.

Regarding the issue with iconv, the lib is available for iOS but it seems that CMake while detecting it when making the build files don't link it properly when compiling... Maybe because it is cross compiling for iOS on Mac ?

from libosmscout.

@Framstag I found a workaround passing -DENABLE_STRICT_TRY_COMPILE=ON to cmake that "Enables strict try_compile() on all Check* directives (will run linker to actually check if linking is possible)."

This solve the issue with fadvise but it's not optimal for iconv because this also disable the usage of it...

from libosmscout.

I'm not an expert in cross-compiling, my knowledge is based on the good old configure & make time. However, in cross-compiling you have the problem that certain tests possibly cannot be executed. Tests may (roughly) succeed, if:

• File exists
• Code compiles
• Code executes

Sometimes the last group has to be skipped because you cannot execute target code on the host. Sometimes this depends on the actual setup and build configuration (processor emulator available). You also have to keep an eye that tests do not test host capabilities.

The question is: How does cmake handle this in general? How does it in concrete handle this for iOS. IMHO it may either be able to execute target code or it has to hardcoded results of the (not executed) tests in a iOS specific profile.

In the end we can hardcode this ourself in the build files, however this would only the 2nd best solution.

It may also depend on, compiling for one processor platform or multiple platforms :-/

So...we are up to web search and official documentation. I recently tried to move the iOS more in the direction of "official documentation" recently, but it may, that there is still a gap.

from libosmscout.

I'll close this issue as there is a workaround

from libosmscout.