cross language for production test not going well.

[ElliotHYLee]

I wonder if the cross-language example resolves this. #480

In fact, it builds fine and the examples with cross language work fine within the iceoryx2 project.

Then, I built Iceoryx1 and Iceoryx2 to /usr/local so that a standalone C++ project can do it. And, cxx pub-sub works fine.

However, I just copied and pasted the cross-language examples for both C++ and Rust. But with their own root,

Error: PublishSubscribeOpenError(ServiceInCorruptedState) #219 (i'm with the same user id)

I wonder if this is a build problem or some datatype setup needs to be done somehow globally or so. Please advise.

OS: ubuntu
Cxx bulid: main branch iox2, local cmake
rust build: from cargo
[dependencies]
iceoryx2 = "0.6.1"

---

Update:

public rust build didn't work

[dependencies]
iceoryx2 = "0.6.1"

direct link to this project works.

[dependencies]
iceoryx2 = { path = "/path/to/your/iceoryx2/iceoryx2" } # main branch

---

more observations using rust public iceoryx2

	This Project RUST Publisher	This Project RUST Subscriber	This Project CXX Pub	This Project CXX Sub
Standalone RUST Pub	-	ok	-	ServiceInCorruptedState
Standalone RUST Sub	ok	-	ServiceInCorruptedState	-
Standalone CXX Pub	-	ok	-	ok
Standalone CXX Sub	ok	-	ok	-

---

Hopefully, it was a simple version mismatch..

[elBoberido]

@ElliotHYLee current main is not compatible with the 0.6.1 release. Please checkout the v0.6.1 tag for the C++ bindings.

@elfenpiff we need to adopt something from #843 to prevent such situations

[elfenpiff]

@elBoberido In the PackageVersion struct, that is stored in shm and ensures that different iceoryx2 versions are not mixed, we have 16 bit space available: https://github.com/eclipse-iceoryx/iceoryx2/blob/main/iceoryx2-bb/elementary/src/package_version.rs#L31

So we have 16bit for each of major, minor and patch entry - maybe we should add a u16::MAX as forth bit to mark main. It would not be visible for the the user - except in error messages when hinting that one uses the v0.6.1 from the main branch.

What do you think?

[elfenpiff]

@elBoberido @ElliotHYLee I created this bug report so that we handle this cleanly in the future: #1019

[ElliotHYLee]

FYI currenty v0.6.1 somehow doesn't build. main branch builds. But main branch does build.

error: could not compile iceoryx2-ffi (lib) due to 1 previous error
gmake[2]: *** [iceoryx2-ffi/c/CMakeFiles/iceoryx2-build-step.dir/build.make:70: iceoryx2-ffi/c/CMakeFiles/iceoryx2-build-step] Error 101
gmake[1]: *** [CMakeFiles/Makefile2:751: iceoryx2-ffi/c/CMakeFiles/iceoryx2-build-step.dir/all] Error 2
gmake: *** [Makefile:136: all] Error 2
-- Install configuration: ""
-- Up-to-date: /usr/local/include/iceoryx2/v0.6.1
-- Up-to-date: /usr/local/include/iceoryx2/v0.6.1/iox2
-- Installing: /usr/local/include/iceoryx2/v0.6.1/iox2/iceoryx2.h
CMake Error at target/ffi/build/iceoryx2-ffi/c/cmake_install.cmake:50 (file):
file INSTALL cannot find
"/home/el/localprojects/iceoryx2/target/ffi/build/rust/native/release/libiceoryx2_ffi.a":
No such file or directory.
Call Stack (most recent call first):
target/ffi/build/cmake_install.cmake:47 (include)

---

I didn't check which commit's missing

Compared to the main branch, that line should be

(&(&(*handle))[index] as *const Attribute).cast()

for the correct v0.6.1

[ElliotHYLee]

For now, I'm using main. v0.6.1 doesn't support Python.

[elBoberido]

@ElliotHYLee so main builds for you on the same setup that v0.6.1 does not build? I mean the setup from #1018 (comment)

[ElliotHYLee]

That's correct for whatever reason.. unless I change the line to

(&(&(*handle))[index] as *const Attribute).cast() for v0.6.1.

Not 100% sure if my build used the wrong config. I just wrote it by myself - I couldn't find a proper build script.

FYI, here's the build. And I DIDN'T change the top-level CMakeLists.txt.

cmake -S . -B target/ffi/build -DBUILD_EXAMPLES=ON \
                              -DCMAKE_PREFIX_PATH="/usr/local/lib" 
                            #   -DRUST_BUILD_ARTIFACT_PATH="~/.cargo/iox_release_rs"

cmake --build target/ffi/build -j $(nproc)
sudo cmake --install target/ffi/build

I wonder if this is important though as you will anyway update to the next version.

[elBoberido]

We did not receive any bug reports, so there is a chance it is only on your setup. But as long as main builds, it should be fine and fixed with the next release.