You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In PR #424, I used a hacky workaround to ensure that the pallene_core symbols are included in the final executable. Grep for "PALLENE LINKER HACK" in the code.
I'm not sure if this hack works on other operating systems, such as MacOS or Windows. At the very least, we should test if it also works on other platforms. Alternatively, if there is a less hacky way to ensure that the symbols are included in the executable, that would be also welcome.
The text was updated successfully, but these errors were encountered:
I replaced the old workaround with another one that I'm more confident that will pass. Now we compile the pallene_core as part of the lapi.o, instead of as its own object file.
However, we should still test on other platforms to ensure that it is working. It's been a while since the last time we ran tests on MacOS, for example.
In PR #424, I used a hacky workaround to ensure that the pallene_core symbols are included in the final executable. Grep for "PALLENE LINKER HACK" in the code.
I'm not sure if this hack works on other operating systems, such as MacOS or Windows. At the very least, we should test if it also works on other platforms. Alternatively, if there is a less hacky way to ensure that the symbols are included in the executable, that would be also welcome.
The text was updated successfully, but these errors were encountered: