Re: Using platforms in 2.8.0

2022-10-31 Thread Joshua Root
On 2022-11-1 13:41 , Nils Breunese wrote: Joshua Root wrote: According to https://guide.macports.org/#reference.variables ${os.arch} is either “powerpc”, “i386”, or “arm”. Does this mean all Intel machines have ${os.arch} set to ‘i386', regardless of whether they’re 32 or 64 bit machines,

Re: Using platforms in 2.8.0

2022-10-31 Thread Nils Breunese
Joshua Root wrote: > On 2022-11-1 13:31 , Nils Breunese wrote: >> Joshua Root wrote: >>> On 2022-11-1 11:45 , Nils Breunese wrote: >>> So when a port installs one pre-built binary on x86_64 and another on arm64, regardless of OS version, setting 'platforms {darwin any}’ would be

Re: Using platforms in 2.8.0

2022-10-31 Thread Joshua Root
On 2022-11-1 13:31 , Nils Breunese wrote: Joshua Root wrote: On 2022-11-1 11:45 , Nils Breunese wrote: So when a port installs one pre-built binary on x86_64 and another on arm64, regardless of OS version, setting 'platforms {darwin any}’ would be appropriate and correct? Sure. Unless

Re: Using platforms in 2.8.0

2022-10-31 Thread Nils Breunese
Joshua Root wrote: > On 2022-11-1 11:40 , Nils Breunese wrote: >> Joshua Root wrote: >>> On 2022-10-22 21:56 , Kirill A. Korinsky wrote: I'm asking is there a way to support specified arch inside platform block's condition. Like: platform {aarch64} { ... } >>> >>>

Re: Using platforms in 2.8.0

2022-10-31 Thread Nils Breunese
Joshua Root wrote: > On 2022-11-1 11:45 , Nils Breunese wrote: > >> So when a port installs one pre-built binary on x86_64 and another on arm64, >> regardless of OS version, setting 'platforms {darwin any}’ would be >> appropriate and correct? > > Sure. Unless the x86_64 binary was built

Re: Using platforms in 2.8.0

2022-10-31 Thread Joshua Root
On 2022-11-1 11:45 , Nils Breunese wrote: Joshua Root wrote: On 2022-11-1 11:14 , Nils Breunese wrote: Joshua Root wrote: There is another way that platforms can be used: platforms any platforms {darwin any} The first one indicates that the port will install identical files no matter

Re: Using platforms in 2.8.0

2022-10-31 Thread Joshua Root
On 2022-11-1 11:40 , Nils Breunese wrote: Joshua Root wrote: On 2022-10-22 21:56 , Kirill A. Korinsky wrote: I'm asking is there a way to support specified arch inside platform block's condition. Like: platform {aarch64} { ... } You can certainly do things like: platform darwin arm {

Re: Using platforms in 2.8.0

2022-10-31 Thread Nils Breunese
Joshua Root wrote: > On 2022-11-1 11:14 , Nils Breunese wrote: >> Joshua Root wrote: >>> There is another way that platforms can be used: >>> >>> platforms any >>> platforms {darwin any} >>> >>> The first one indicates that the port will install identical files no >>> matter what platform it

Re: Using platforms in 2.8.0

2022-10-31 Thread Joshua Root
On 2022-11-1 11:14 , Nils Breunese wrote: Joshua Root wrote: There is another way that platforms can be used: platforms any platforms {darwin any} The first one indicates that the port will install identical files no matter what platform it is built on, and will set the platform in the

Re: Using platforms in 2.8.0

2022-10-31 Thread Nils Breunese
Joshua Root wrote: > On 2022-10-22 21:56 , Kirill A. Korinsky wrote: >> I'm asking is there a way to support specified arch inside platform block's >> condition. Like: >> platform {aarch64} { >> ... >> } > > You can certainly do things like: > > platform darwin arm { > ... > } I wasn’t

Re: Using platforms in 2.8.0

2022-10-31 Thread Nils Breunese
Joshua Root wrote: > There is another way that platforms can be used: > > platforms any > platforms {darwin any} > > The first one indicates that the port will install identical files no matter > what platform it is built on, and will set the platform in the archive > filename to "any_any".

Re: Using platforms in 2.8.0

2022-10-22 Thread Marius Schamschula
I haven’t tried to build MacPorts 2.8.0 under FreeBSD (the source tarball gives a 404), but I last tried 2.7.2 built and it installed cleanly, but was unusable as portindex failed. I could debug to the point where it failed, but never could figure out what was going on. Marius -- Marius

Re: Using platforms in 2.8.0

2022-10-22 Thread Kirill A. Korinsky via macports-dev
clear, thanks -- wbr, Kirill > On 22. Oct 2022, at 13:03, Joshua Root wrote: > > On 2022-10-22 21:56 , Kirill A. Korinsky wrote: >> I'm asking is there a way to support specified arch inside platform block's >> condition. Like: >> platform {aarch64} { >> ... >> } > > You can certainly do

Re: Using platforms in 2.8.0

2022-10-22 Thread Joshua Root
On 2022-10-22 21:56 , Kirill A. Korinsky wrote: I'm asking is there a way to support specified arch inside platform block's condition. Like: platform {aarch64}  { ... } You can certainly do things like: platform darwin arm { ... } or: if {$build_arch eq "arm64"} { ... } There is no arch

Re: Using platforms in 2.8.0

2022-10-22 Thread Kirill A. Korinsky via macports-dev
I'm asking is there a way to support specified arch inside platform block's condition. Like: platform {aarch64} { ... } -- wbr, Kirill > On 22. Oct 2022, at 12:55, Joshua Root wrote: > > On 2022-10-22 20:34 , Kirill A. Korinsky wrote: >> Does it support somehow arch? > > I'm not sure what

Re: Using platforms in 2.8.0

2022-10-22 Thread Joshua Root
On 2022-10-22 20:34 , Kirill A. Korinsky wrote: Does it support somehow arch? I'm not sure what you're asking exactly. There was already the supported_archs option of course, and either a specific set of archs or "noarch" is included in the archive filename. - Josh

Re: Using platforms in 2.8.0

2022-10-22 Thread Kirill A. Korinsky via macports-dev
Does it support somehow arch? -- wbr, Kirill > On 22. Oct 2022, at 10:50, Joshua Root wrote: > > MacPorts 2.8.0 lets you specify which OS versions your ports work on via the > platforms option. This indicates a port that works on darwin versions from > 10.x to 19.x inclusive: > > platforms