maemo.org - Talk - gcc >= 6 ?

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - gcc >= 6 ? (https://talk.maemo.org/showthread.php?t=99699)

For those interested in an example on how to use gcc 6 for their projects could look into https://github.com/rinigus/mapbox-demo-sfos. Its a working solution that allowed me to port C++14 library and build a simple application around it.

Some notes:

* In YAML (https://github.com/rinigus/mapbox-de...pbox-sfos.yaml), add opt-gcc6 as PkgBR

* Project file (https://github.com/rinigus/mapbox-de...apbox-sfos.pro) has compilers and linkers defined to /opt/gcc6/bin/g++ .

* For C++14, add c++14 in CONFIG of the project file.

* In project file, you could either opt for static or shared linking with stdc++. Static linking (as in the current version of pro file, see LIBS var) makes it easier to distribute, may have some side effects. Sometimes, as when developing QML plugin, static is the only way to go.

* Desktop file (https://github.com/rinigus/mapbox-de...x-sfos.desktop) has an application switched to "generic" to avoid silica boosters getting confused with the wrong stdc++ library version (dynamic link to stdc++) or inability to send signals (static link to stdc++).

* If you went for shared stdc++ build, add

Code:

%define __provides_exclude_from ^%{_datadir}/.*$

%define __requires_exclude ^libstdc.*$

in SPEC file (https://github.com/rinigus/mapbox-de...pbox-sfos.spec, in macros section) and

Code:

# ship all shared libraries not allowed in Harbour with the app

mkdir -p %{buildroot}%{_datadir}/%{name}/lib



cp /opt/gcc6/lib/libstdc++.so.6.0.22 %{buildroot}%{_datadir}/%{name}/lib/libstdc++.so.6

cp /opt/gcc6/lib/libgcc_s.so.1 %{buildroot}%{_datadir}/%{name}/lib/libgcc_s.so.1

cp /opt/gcc6/lib/libgcc_s.so %{buildroot}%{_datadir}/%{name}/lib/libgcc_s.so

in install post section.

* See https://github.com/rinigus/mapbox-de...sfos-rpmlintrc if you get into trouble with OBS.

For me, it all worked and I could compile and distribute program with gcc 6.4.0 as well as QML plugin compiled using similar approach. I believe that this is a viable solution and should allow to port the software that requires recent gcc version.

If you want to use it from within the OBS, see how to add the repo to your project: https://build.merproject.org/project...e:rinigus:maps

Quote:

Originally Posted by neochapay (Post 1541095)

http://repo.merproject.org/obs/home:...mv7hl/armv7hl/ ready ^_^

Great job! This looks to be a proper packaging of gcc (in contrast of my approach where I stuffed all to /opt)

@neochapay, have you tried to compile anything demanding with it?

How does libstdc++ versioning go? In particular, I expect to have the same problems as with opt-gcc6 packaging - either

* libstdc++ has to be updated on device
* provided with an app
* linked statically

Note that SFOS boosters may not like your app-provided dynamically linked libstdc++

Looking forward to use it. Thank you again!

Quote:

Originally Posted by rinigus (Post 1541096)

Great job! This looks to be a proper packaging of gcc (in contrast of my approach where I stuffed all to /opt)

@neochapay, have you tried to compile anything demanding with it?

Now i got self complited gcc 6 :) next steep - try to compile glibc

Quote:

Originally Posted by neochapay (Post 1541097)

Now i got self complited gcc 6 :) next steep - try to compile glibc

Are you using the legacy or the new ABI? Do you want it to be a drop-in replacement or do you want to rebuild the whole Mer?

Quote:

Originally Posted by marmistrz (Post 1541124)

Are you using the legacy or the new ABI? Do you want it to be a drop-in replacement or do you want to rebuild the whole Mer?

yes and yes

Quote:

Originally Posted by neochapay (Post 1541140)

yes and yes

Pretty obvious question, did you succeed?