Ticket #17550 (closed defect: fixed)
doxygen fails to build universal
| Reported by: | jeremyhu@… | Owned by: | css@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | universal | Cc: | css@…, mcalhoun@…, eborisch@… |
| Port: | doxygen |
Description
not a standard autoconf project
I'm going to add universal_variant no in the mean time.
Change History
comment:2 Changed 5 years ago by jeremyhu@…
- Status changed from closed to reopened
- Resolution fixed deleted
This isn't fixed. It's still an issue. I just marked it as 'universal_variant no' to allow building until you do fix it to build universal.
comment:3 Changed 4 years ago by css@…
- Priority changed from Normal to Low
It'll take some more in depth investigation. I'm dropping the priority to low unless there's a big demand.
comment:5 in reply to: ↑ description ; follow-up: ↓ 7 Changed 4 years ago by eborisch@…
Replying to jeremyhu@…:
not a standard autoconf project
I'm going to add universal_variant no in the mean time.
It's pretty simple, it seems...
Edit tmake/lib/macosx-c++/tmake.conf after the configure step to include the desired architectures.
TMAKE_CFLAGS = -pipe -arch i386 -arch x86_64 [...] TMAKE_LFLAGS = -Wl,-search_paths_first -arch i386 -arch x86_64
Then build... (Worked for me, at least.)
$ file which doxygen /opt/local/bin/doxygen: Mach-O universal binary with 2 architectures /opt/local/bin/doxygen (for architecture i386): Mach-O executable i386 /opt/local/bin/doxygen (for architecture x86_64): Mach-O 64-bit executable x86_64
comment:7 in reply to: ↑ 5 ; follow-up: ↓ 8 Changed 4 years ago by css@…
Replying to eborisch@…:
Edit tmake/lib/macosx-c++/tmake.conf after the configure step to include the desired architectures.
tmake/lib/macosx-uni-c++/tmake.conf contains those same lines. I'll see if I can switch to using that. The universal variant would need to use --platform macosx-uni-c++ during the configure phase.
comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 4 years ago by eborisch@…
Replying to css@…:
Replying to eborisch@…:
Edit tmake/lib/macosx-c++/tmake.conf after the configure step to include the desired architectures.
tmake/lib/macosx-uni-c++/tmake.conf contains those same lines. I'll see if I can switch to using that. The universal variant would need to use --platform macosx-uni-c++ during the configure phase.
Just curious if there is something impeding this change?
comment:9 in reply to: ↑ 8 Changed 4 years ago by css@…
Replying to eborisch@…:
Replying to css@…:
Replying to eborisch@…:
Edit tmake/lib/macosx-c++/tmake.conf after the configure step to include the desired architectures.
tmake/lib/macosx-uni-c++/tmake.conf contains those same lines. I'll see if I can switch to using that. The universal variant would need to use --platform macosx-uni-c++ during the configure phase.
Just curious if there is something impeding this change?
Mainly it's that universal builds are below my radar, and my MacPorts config isn't currently configured for them. I'll need to deactivate and rebuild everything to test it. (IMO, it seems easier to just build from source on the target system.)
I think the port could do contain like:
platform darwin {
global tmake_conf
if {[variant_isset universal]} {
set tmake_conf ${worksrcpath}/tmake/lib/macosx-uni-c++/tmake.conf
configure.args-append --platform macosx-uni-c++
} else {
set tmake_conf ${worksrcpath}/tmake/lib/macosx-c++/tmake.conf
configure.args-append --platform macosx-c++
}
[... pre-Leopard fix ...]
}
comment:11 Changed 4 years ago by css@…
I committed this to r51717, so if universal builds are something you use, please give it a test. Regular builds appear to work fine.
comment:12 Changed 4 years ago by css@…
- Status changed from reopened to closed
- Resolution set to fixed


This isn't an openmaintainer port ... please verify with port maintainers before making commits.
Marking this closed.