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
By default, the project directory is the one, which contains the buildfile. This way, it is possibly to only reference an alternative buildfile (-f, -F) and trigger the build in the right directory.
Sometimes, it is desireable, to execute a buildfile from elsewhere in the current or another directory. GNU Make has an option ("-C", "--directory") for that use case.
Use case 1: A "central" build file in the users home directory which contains generic task (aka tools, see also #126) which might be useful in different places
Use case 2: A remote build file or a downloaded buildfile or a buildfile lying in a readonly location.
By default, the project directory is the one, which contains the buildfile. This way, it is possibly to only reference an alternative buildfile (-f, -F) and trigger the build in the right directory.
Sometimes, it is desireable, to execute a buildfile from elsewhere in the current or another directory. GNU Make has an option ("-C", "--directory") for that use case.
Use case 1: A "central" build file in the users home directory which contains generic task (aka tools, see also #126) which might be useful in different places
Use case 2: A remote build file or a downloaded buildfile or a buildfile lying in a readonly location.
Ticket imported form Redmine http://sbuild.tototec.de/sbuild
Original Redmine issue link: Redmine ID 134
Reporter: Tobias Roeser => @lefou
Creating date: 2013-07-02T21:39:08+02:00
Assigned to:
Start date: 2013-07-02
Due date:
This issue relates issue #126.
This issue blocks issue #133.
The text was updated successfully, but these errors were encountered: