Page MenuHomeFreeBSD

more options helpers
AbandonedPublic

Authored by makc on Oct 19 2014, 10:35 AM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 27 2024, 12:16 PM
Unknown Object (File)
Jan 6 2024, 2:50 AM
Unknown Object (File)
Jan 5 2024, 6:26 PM
Unknown Object (File)
Nov 14 2023, 10:39 PM
Unknown Object (File)
Jun 30 2023, 8:03 AM
Unknown Object (File)
Jun 19 2023, 11:23 PM
Unknown Object (File)
Jun 15 2023, 2:02 AM
Unknown Object (File)
Jun 3 2023, 11:35 PM
Subscribers

Details

Reviewers
None
Group Reviewers
portmgr
Summary

Add CMAKE_ENV and QMAKE_ENV to the list of available helpers

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

makc retitled this revision from to more options helpers.
makc updated this object.
makc edited the test plan for this revision. (Show Details)
makc added a reviewer: portmgr.

Since in Uses/[cq]make.mk, there is:
[CQ]MAKE_ENV?= ${CONFIGURE_ENV}
the option helpers will totally override [CQ]MAKE_ENV (content of CONFIGURE_ENV will not be used)

Is this behaviour intended?

If not, there is already an option helper for CONFIGURE_ENV

I always thought it's by design, but I don't know if this is really needed for any port. Anyway [CQ]MAKE_ENV are already in use, so helpers for them would be nice to have.

I'm with @antoine on this, both cmake and qmake replace configure, and both *_ENV already inherit from CONFIGURE_ENV.

In D966#6, @mat wrote:

I'm with @antoine on this, both cmake and qmake replace configure, and both *_ENV already inherit from CONFIGURE_ENV.

Until you use [CQ]MAKE_ENV, which reset CONFIGURE_ENV and any CONFIGURE_ENV modifications becomes no-op. But even if it were not the case, for the sake of consistency I'd like to have helpers for [CQ]MAKE_ENV similar to *_ARGS.

In principle we could consider reworking cmake.mk/qmake.mk for tightening with CONFIGURE stuff in bsd.port.mk, but this is a different task and I don't see much benefit from it now. Any change for any configure tool will require testing for all of them. There are also weird ports (not many but still) that use both gnu configure and qmake, so they would need special treatment anyway.

Any comment? Should I consider the discussion closed?

CONFIGURE_ENV has to be seen has configure phase env not configure script env, and imho everything that needs ENV in configure phase should just use CONFIGURE_ENV instead of RANDOM_ENV imho it would be better to work on clarifying this than adding those new helpers.

In D966#10, @bapt wrote:

CONFIGURE_ENV has to be seen has configure phase env not configure script env, and imho everything that needs ENV in configure phase should just use CONFIGURE_ENV instead of RANDOM_ENV imho it would be better to work on clarifying this than adding those new helpers.

I see, I'll work on converting [QC]MAKE_ENV to CONFIGURE_ENV.