Opened 3 months ago

Closed 2 months ago

#1484 closed enhancement (fixed)

Should csc-options be valid at the top level too?

Reported by: mario Owned by:
Priority: not urgent at all Milestone: 5.0
Component: build system Version: 5.0
Keywords: csc-options Cc:
Estimated difficulty:

Description

Currently, csc-options is not valid at the top level of .egg files. That leads to a lot of code duplication in case eggs declare multiple components.

How about allowing a top level csc-options declaration that can be clobbered by component-specific csc-options declarations?

Change History (4)

comment:1 Changed 3 months ago by evhan

I think so, and link-options too.

comment:2 Changed 2 months ago by evhan

I think common options for all components should go in a (component-options ...) item (or something similarly named), rather than at the top level of the egg file. We should probably still limit it to csc-options and link-options, though.

comment:3 Changed 2 months ago by felix

I would suggest to make it cumulative - local options get added to toplevel options.

Last edited 2 months ago by felix (previous) (diff)

comment:4 Changed 2 months ago by kooda

  • Resolution set to fixed
  • Status changed from new to closed

Fixed by 9b2b6bc717ed266f17721444e9ac4e6277aa0c01

Note: See TracTickets for help on using tickets.