doxygen fails to build universal

[jeremyhu (Jeremy Huddleston Sequoia)]

not a standard autoconf project

I'm going to add universal_variant no in the mean time.

[cssdev]

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

Marking this closed.

[jeremyhu (Jeremy Huddleston Sequoia)]

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.

[cssdev]

It'll take some more in depth investigation. I'm dropping the priority to low unless there's a big demand.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Cc Me!

[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

[eborisch@…]

Cc Me!

[cssdev]

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.

[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?

[cssdev]

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 ...]
}

[(none)]

Milestone Port Bugs deleted

[cssdev]

I committed this to r51717, so if universal builds are something you use, please give it a test. Regular builds appear to work fine.