Skip to content

Bug fixed (Build-on : GNU/Linux) -> target_file: PreferencesDialogStyle.cpp, target_line: 571#408

Merged
arvanus merged 1 commit into
mariuz:masterfrom
baldeuniversel:master
Feb 14, 2025
Merged

Bug fixed (Build-on : GNU/Linux) -> target_file: PreferencesDialogStyle.cpp, target_line: 571#408
arvanus merged 1 commit into
mariuz:masterfrom
baldeuniversel:master

Conversation

@baldeuniversel

Copy link
Copy Markdown
Contributor

Hi !

Here a bug :

bug_flamerobin_0 9 12

I fixed it by modifying this file PreferencesDialogStyle.cpp, the affected line is (line 571) :
style->setFontSize(atoi(fontSizeComboBoxM->GetString(fontSizeComboBoxM->GetSelection())));

Here the update :

style->setFontSize(atoi(fontSizeComboBoxM->GetString(fontSizeComboBoxM->GetSelection()).ToStdString().c_str()));


Build-on : GNU/Linux

wx-config --version
3.2.6

…71, build_on: GNU/Linux, wxWedgets_v: 3.2.6\}
@arvanus
arvanus merged commit a0c8372 into mariuz:master Feb 14, 2025
@baldeuniversel

Copy link
Copy Markdown
Contributor Author

Hi !

Here a release for Linux system (already tested on GNU/Linux successfully).

FlameRobin 0.9.12 : build-for-linux

@baldeuniversel

Copy link
Copy Markdown
Contributor Author

And a snap version here :

https://snapcraft.io/flamerobin

@arvanus

arvanus commented Feb 19, 2025

Copy link
Copy Markdown
Collaborator

How do you generate the .deb?
It would be nice to have a .deb or at least a compiled .tar.gz generated automatically in our CICD

@baldeuniversel

baldeuniversel commented Feb 20, 2025

Copy link
Copy Markdown
Contributor Author

How do you generate the .deb? It would be nice to have a .deb or at least a compiled .tar.gz generated automatically in our CICD

Note :
A workflow file focused on Linux needs to be created.


In the main directory(the root), two directories(with some subdirectories) can be added like this :
(A) templates -> trees -> deb -> flamerobin
(B) build-for -> linux

On the (A) tree , I can add some templates files, and some algos that will be used after the execution of this command make install (need a virtual machine to perform this operation), and during the installation of the .deb package.

For sure, before executing the make install command, it's necessary to indicate a well-known prefix installation path like this -> /usr/local. After the execution of the make install command (successfully), a script or algorithm should be executed to retrieve the Debian templates, make modifications (for example, set the correct flameRobin version, etc.), assemble them with the directories resulting from the installation, and then build everything into a valid .deb package, then upload the result to (B) tree.

Essentially, these are the scenarios and processes to be carried out.

@baldeuniversel

baldeuniversel commented Feb 21, 2025

Copy link
Copy Markdown
Contributor Author

Hi !

I created a workflow file and implemented some templates and algos allowing to build, construct and install the deb resulting package (specially the flamerobin app).

Here the status of the build :
flamerobin for Linux -> workflow build status

A pull request is pending for a merge.

@baldeuniversel

Copy link
Copy Markdown
Contributor Author

Hi !

I updated the workflow file (linux-build.yml) to ensure that, after building the flamerobin app, the upstream files [Build/*] are used instead of the copied custom files.

Here the status of the new build. (Build successfully)

Tested on Ubuntu 24.04 successfully.

A pull request is pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants