TenFourFox: Question about libatomic.1.dylib, libgcc_s.1.dylib, libstdc++.6.dylib

[pipetogrep]

Hi all,

From http://tenfourfox.blogspot.com/2021...howComment=1619022422135#c3683092910233827983 I understand that I need to replace libatomic.1.dylib, libgcc_s.1.dylib, libstdc++.6.dylib with the more optimized versions.

What I'm confused about is do I need to copy those into TenFourFox.app/Contents/MacOS after it's compiled or do I need to copy them into /opt/macports-tff/libgcc7/ and /opt/macports-tff/libgcc/ before compiling the browser?

Thanks

 

[wicknix]

In to the compiled .app itself yes. The 104fx_copy.sh script does this.

Cheers

 

[pipetogrep]

In to the compiled .app itself yes. The 104fx_copy.sh script does this.

Cheers

I think I see now. https://github.com/classilla/tenfourfox/blob/master/104fx_copy.sh#L22-L24

ditto /opt/local/lib/$libgcc/libstdc++.6.dylib ./
ditto /opt/local/lib/$libgcc/libgcc_s.1.dylib ./
ditto /opt/local/lib/$libgcc/libatomic.1.dylib ./

I need to have those files in place in the MacPorts prefix before running the 104fx_copy.sh script. Time to upload a new toolkit version!

 

[alex_free]

I think I see now. https://github.com/classilla/tenfourfox/blob/master/104fx_copy.sh#L22-L24

ditto /opt/local/lib/$libgcc/libstdc++.6.dylib ./
ditto /opt/local/lib/$libgcc/libgcc_s.1.dylib ./
ditto /opt/local/lib/$libgcc/libatomic.1.dylib ./

I need to have those files in place in the MacPorts prefix before running the 104fx_copy.sh script. Time to upload a new toolkit version!

The technical reason is your have to distribute modern equivalents of what once existed on 10.4 to make TFF work, please feel free to ask more about this! This is also the case with SuperMario64EX!

 

[barracuda156]

Is this part still relevant? I think I didn’t see anything about libs replacement in TFF recent tutorial.

 

[alex_free]

Is this part still relevant? I think I didn’t see anything about libs replacement in TFF recent tutorial.

Either this was automated, changed to static linking, or is just not being mentioned. No other ways around it.