Dear edk2-devel subscribers,
 
A few moments ago, I have published a patch to the EDK2 BaseTools with the 
subject "BaseTools: Add Multiple Workspaces support  for custom Makefiles.", 
which is aimed at providing Custom Makefile modules support for Multiple 
Workspaces. Writing the patch, I noticed that in quite a few areas WORKSPACE is 
still used (especially in MODULE_DIR, which is the reason custom Makefile 
modules would not be buildable in a different workspace from the primary). In 
the places in which it isn't, mws.join() is called to construct a path by also 
checking the PACKAGES_PATH list.
 
To simplify the process and ending with cleaner code, I propose to have the 
PLATFORM_DIR variable fixed to point to the correct, absolute path and 
construct other variables (such as MODULE_DIR) from that value, so PLATFORM_DIR 
serves as a central variable (changes to it affect all paths = easier to 
maintain).
 
Sadly, I do not think I either have the Python skills, or the insight in the 
inner workings of BaseTools to implement such a patch. I would be grateful if 
someone would look into implementing this, or a similar behavior to fully 
support Multiple Workspaces and have an easier to maintain codebase.
 
Regards,
Marvin.
                                          
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to