public header location incompatibility

[yamt]

#4076 changed the location of wasm_export.h etc.

problems:

• it's an api breaking change. that is, #include <wasm_export.h> vs #include <iwasm/wasm_export.h>
• it has not been mentioned as a breaking change in 2.3.0 release notes.
• it causes inconsistencies among platforms. for example, nuttx-apps still provides these headers this way.
• changes like this should be done a bit more carefully. eg. provide compat headers for a few releases.
• there seems no CI tests to use wamr via a cmake package.

[lum1n0us]

I might miss the point of "it's an api breaking change. that is, #include <wasm_export.h> vs #include <iwasm/wasm_export.h>". Would you mind explaining more clearly?

[yamt]

I might miss the point of "it's an api breaking change. that is, #include <wasm_export.h> vs #include <iwasm/wasm_export.h>". Would you mind explaining more clearly?

user applications need to be adapted to use #include <iwasm/wasm_export.h>.
or they need to add another -isystem to their CFLAGS.
or whatever.

[yamt]

there seems no CI tests to use wamr via a cmake package.

#4291

[yamt]

or they need to add another -isystem to their CFLAGS.

either via the cmake package or manually. please note that not every user app uses cmake.

[lum1n0us]

cmake --build build-wamr -t install

Now, I understand what you are talking about. Using installation is a new approach for me regarding how to integrate WAMR into a project. I used to think people always embedded WAMR source code into their project and directly used headers in the source code tree and libraries in the build directories. So we didn't treat the new installation destination seriously.

Now, the new installation tree is as follows. We're open to rearranging it, so please let me know your suggestions.

├── bin
│   ├── iwasm -> iwasm-2.2.0
│   └── iwasm-2.2.0
├── include
│   └── iwasm
│       ├── lib_export.h
│       ├── wasm_c_api.h
│       └── wasm_export.h
└── lib
    ├── cmake
    │   └── iwasm
    │       ├── iwasmConfig.cmake
    │       ├── iwasmConfigVersion.cmake
    │       ├── iwasmTargets.cmake
    │       └── iwasmTargets-release.cmake
    └── libiwasm.a 

[yamt]

Now, the new installation tree is as follows. We're open to rearranging it, so please let me know your suggestions.

my suggestion: #4295