| |
| |
On 3/4/21 2:02 PM Manolo wrote:
On Thursday, March 4, 2021 at 12:18:22 PM UTC+1 Albrecht Schlosser wrote:
Great! Now we can share our (FLTK) build experiences on M1 Macs!
For now, I see only deficiencies relatively to my intel MacBook Pro.
Did you expect it to work flawlessly from day 0 on? ;-) 8-)
I have just tried macports since fink isn't ready for macOS 11, and it
seems quite
good. Noticeably you can install binaries in arm or in universal form.
That's good news. Maybe I should try this as well. I don't know why but
I had gotten the impression that MacPorts was not as up-to-date as
Homebrew. Maybe that impression was wrong. (?)
I jut did that for pkg-config, as an example of package, which I had
first installed in arm form :
% file /opt/local/bin/pkg-config
/opt/local/bin/pkg-config: Mach-O 64-bit executable arm64
% sudo port install pkgconfig +universal <-- the install command in
its universal flavor
---> Fetching archive for pkgconfig
---> Attempting to fetch
pkgconfig-0.29.2_0+universal.darwin_20.arm64-x86_64.tbz2 from
https://lil.fr.packages.macports.org/pkgconfig
---> Attempting to fetch
pkgconfig-0.29.2_0+universal.darwin_20.arm64-x86_64.tbz2 from
https://packages.macports.org/pkgconfig
---> Attempting to fetch
pkgconfig-0.29.2_0+universal.darwin_20.arm64-x86_64.tbz2.rmd160 from
https://packages.macports.org/pkgconfig
---> Installing pkgconfig @0.29.2_0+universal
---> Deactivating pkgconfig @0.29.2_0
---> Cleaning pkgconfig
---> Activating pkgconfig @0.29.2_0+universal
---> Cleaning pkgconfig
OK, that sounds very good.
% file /opt/local/bin/pkg-config
/opt/local/bin/pkg-config: Mach-O universal binary with 2 architectures:
[x86_64:Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable
arm64]
/opt/local/bin/pkg-config (for architecture x86_64): Mach-O 64-bit
executable x86_64
/opt/local/bin/pkg-config (for architecture arm64): Mach-O 64-bit
executable arm64
Some questions:
What is your PATH after installation and configuration of MacPorts?
What does `which pkg-config' output ?
Are there potential conflicts with other tools / symbolic links in
/usr/local or elsewhere?
Finally, pkg-config is a nice example but having a universal executable
is less important than being able to *build* universal apps. The main
purpose of installing 'universal' packages is IMHO for libraries so they
can be linked in universal binaries. Did you try this too? Is it possible?
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/278db69f-5668-cd01-02cc-ecce91f273a6%40online.de.
[ Direct Link to Message ] | |
|
| |
