Open adrienluitot opened 1 day ago
I don't have hardware to do that currently.
I have a Raspberry Pi so I can build it for you if you want. It’s pretty slow to build but it doesn’t matter I guess. Maybe I should try cross compiling too.
Cross-compiling means it builds, but cannot be tested. And I cannot offer untrusted binaries for download.
That's true indeed, once the compilation is done, I'll try the test procedure. The compilation is very slow on the Raspberry :') You are right not to offer untrusted binaries, how do you do with Kazzz-S for Mac binaries?
Did you have any attempt cross compiling KLayout so far?
PS: It seems that compilation also builds Qt modules. Isn't it possible to use pre-compiled or shared libraries to speed to compilation?
So after too many hours, compilation of 0.29.8 is finished. I ran the test (with -g
option) and got these fails:
Failed in non-editable mode
bdStrmrunTests:1
klayout_main_tests:main
pymod_tests:import_QtNetwork
tlVariantTests:4
Failed in editable mode
bdStrmrunTests:1
klayout_main_tests:main
pymod_tests:import_QtNetwork
tlVariantTests:4
tlWebDAVTests:1
tlVariantTests:4
fail is caused by: Exception caught: ../../../src/tl/unit_tests/tlVariantTests.cc, line 874: v.can_convert_to_char () does not equal true
~~tlWebDAVTests:1
is caused by: Exception caught: Error 99: Network API error, fetching http://www.klayout.org/svn-public/klayout-resources/trunk/testdata
Which is strange because other tlWebDAVTests passed. I will re run the test to ensure it's not an error from my network.~~
EDIT: After re running the tests today, I don't have a fail on tlWebDAVTests:1
any more.
The other ones seem all related to:
Warning: Unable to find GSI class binding for: N4QSsl11SslProtocolE
Warning: Unable to find GSI class binding for: N15QNetworkRequest12KnownHeadersE
Warning: Unable to find GSI class binding for: 15QNetworkRequest
...
I also have the same warning when I launch klayout or the ut_runner script.
I didn't take the time to debug or search for similar issues yet, I might later. Maybe someone already knows how to fix that.
EDIT: The tests seem to fail when comparing strings, the warnings seem to be added to the string compared. I don't have an exact example right now, but I have something like:
Received: "< [...] Warning: Unable to find GSI class binding for: N4QSsl11SslProtocolE\nHello World!"
Expected: "Hello World!"
I saw in #130 there might be something related to the python path. I started a compilation python setup.py
, I'll see if it changes something.
However I'm not sure those warnings should make the tests fail? I think there is a strange behaviour with the being crapped into the compared string.
PS: Even when setting -prefix
I need to set LD_LIBRARY_PATH when I run klayout. But this is maybe because I didn't set it for the first build, then I used -prefix
for a second build with cleaning, so maybe it didn't recompile the part with RPATH?
It would be cool to have Arm64 .deb on the page https://www.klayout.de/build.html.
This would allow to install more recent packages than default ones.