#3240 closed defect (fixed)
Build: put protections around modules to avoid overwriting by layer file scenarios
Reported by: | James Burke | Owned by: | James Burke |
---|---|---|---|
Priority: | high | Milestone: | 0.9beta |
Component: | BuildSystem | Version: | 0.9 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Now with layer files, it is possible to load a module once in a layer, but still ask for it by its specific resource name/include it in another layer. Bad things can happen if the second load of the module overwrites the first definition.
In a build, put protections around each module so that it only defines the module if it has not been defined already. The protections should be in each module resource as well as inside the layer files, xd and non-xd.
Change History (2)
comment:1 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 14 years ago by
Resolution: | → fixed |
---|
Note: See
TracTickets for help on using
tickets.
(In [8999]) Fixes #3240: adds guards around module code to avoid redefitions in layered build scenarios