Opened 9 months ago
Last modified 9 months ago
#67967 new defect
zfp: how to configure and build 32- and 64-bit separately for Clang builds?
| Reported by: | barracuda156 | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.8.1 |
| Keywords: | universal | Cc: | |
| Port: | zfp |
Description
Clang builds zfp in one go, but 32-bit build needs special defines to build correctly, while 64-bit one does not. It seems these should be rather built separately and then glued together.
Change History (3)
comment:1 follow-up: 2 Changed 9 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 follow-up: 3 Changed 9 months ago by barracuda156
Replying to ryandesign:
Then you'd need to use the muniversal portgroup.
Just add to the portfile and let it do the magic? Does it matter which one is used, 1.0 or 1.1?
comment:3 Changed 9 months ago by ryandesign (Ryan Carsten Schmidt)
Replying to barracuda156:
Just add to the portfile and let it do the magic?
Yes, except of course you'll need to add the directives that tell it to add specific things for specific architectures. Unfortunately the muniversal portgroups are not documented well so you may need to look at other ports that use them to find out how to do that.
Does it matter which one is used, 1.0 or 1.1?
Presumably 1.1 was created to address some deficiency of 1.0 so presumably 1.1 is the one to go for. But 1.0 and 1.1 are pretty different in their interface, so as you go looking at other ports for examples, you'll need to find examples that use the version of the portgroup you want to use.
Then you'd need to use the muniversal portgroup.