You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the target command always launches the target from the local/gbuild directory. This makes it difficult to switch between NC and EC builds easily when working in parallel with both types of targets.
To simplify this, I have been using the following setup for my local development, and it may be worth adding to the repository as a standard:
The target comamand by default launches the target from local/gbuild.ec. When calling it with target -n, it launches from local/gbuild instead.
I chose this because it mirrors the -n switch in pmake to build an NC version of a Geode
Also, having EC as the default may be even more useful for Watcom because the NC build currently has no useful local symbols.
The buildbbx.pl script is changed so that it suggests taget/gbuild.ec as the default target directory when building an EC version, and target/gbuild for an NC version
This would push people towards a standard naming convention for NC/EC target locations, and make launching one or the other easier.
If acceptable, the main question might be whether this change breaks anything in the nightly build system.
The text was updated successfully, but these errors were encountered:
Sounds good to me, I think there is not impact to then CI process because of all parameter are passed from the outside in that case. But isn't the buildbbx command not saving and reusing the values entered the last time? If so, default gbuild/gbuild.ec might fail if nc/ec build run are mixed?
Currently, the
target
command always launches the target from thelocal/gbuild
directory. This makes it difficult to switch between NC and EC builds easily when working in parallel with both types of targets.To simplify this, I have been using the following setup for my local development, and it may be worth adding to the repository as a standard:
target
comamand by default launches the target fromlocal/gbuild.ec
. When calling it withtarget -n
, it launches fromlocal/gbuild
instead.-n
switch inpmake
to build an NC version of a Geodebuildbbx.pl
script is changed so that it suggeststaget/gbuild.ec
as the default target directory when building an EC version, andtarget/gbuild
for an NC versionThis would push people towards a standard naming convention for NC/EC target locations, and make launching one or the other easier.
If acceptable, the main question might be whether this change breaks anything in the nightly build system.
The text was updated successfully, but these errors were encountered: