New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failure on (32bit) Haiku #291
Comments
That identifier is from the newer Lazarus:
|
You can update Lazarus, or just comment this IFDEF
in atsynedit.pas. |
But you make the CudaText on HAIKU, so you must activate widgetset QT5!! then that line
will be deactivated! cudaUp script has the param to activate qt5! |
Looked into the script but can't seem to find it? |
so you must set param "--ws". |
Bumps head ;) running atm with |
Error while linking: |
|
so |
@Begasus Can you tell me what is the default MONOspace font on Haiku? i will hard code it as default. |
I have the hardcoded font names for Haiku - proc_globdata.pas
Do you miss fonts
|
Noto is installed, default it's using
|
made the patch linked above this comment. it must fix the default font? |
Works fine with it, thanks! |
Looks good. |
It did, (renamed the user.json file to check) 👍 |
@Alexey-T is it possible to set the font size to EDIT I think it's set here: Alexey-T/CudaText@ac994f4#diff-22f3b8461d16a1132106a2d19153debfa55bcaa790e8663bc1d3731c879aef4fR1439 |
Added patch to set font size to 12 |
Thanks, checking ... |
Hi @Alexey-T I'm trying to bring CudaText for Haiku uptodate, but running the mentioned command above not gives me a: lazbuild: Could not resolve symbol 'libiconv_open |
Pls move this issue to CudaText repo. but I dont know the reason! sorry |
Trying to get CudaText to build there results in an error for ATSynEdit:
/Opslag/CudaText_up/src/ATSynEdit/atsynedit/atsynedit.pas(8312,9) Error: (5000) Identifier not found "IM_Context_Set_Cursor_Pos"
Running with:
./cudaup.sh -g -m -l /boot/system/non-packaged/bin/fpcupdeluxe/lazarus
fpc and lazarus build with fpcupdeluxe (trunk from a few weeks ago)
The text was updated successfully, but these errors were encountered: