-
Notifications
You must be signed in to change notification settings - Fork 64
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
out-of-tree builds allow multiple configurations to be built simultaneously from one source tree. Each build configuration exists in a separate builddir, and the srcdir contains no configuration, object files or build artifacts. In an autotools project which uses automake, the Makefiles are object files, ie they are generated specifically for a particular configuration. When building an autotools project out-of-tree, the workspace is the srcdir, and does not contain a Makefile. instead, the Makefile is in $makeDirectory which is the builddir. This commit cleans up the detection of makefile location that is done in the extension so that the correct makefile is found, even if it lives out-of-tree/out-of-workspace, has a name other than Makefile/makefile, an whether or not a file named Makefile also exists in the srcdir. WIP because something doesn't work and I don't know how to debug (HELP wanted): - if a file named "Makefile" also exists in srcdir, the extension functions correctly. - if a file named "Makefile" does NOT exist in the srcdir, but only in builddir (as is typical), the extension is asynchronously deactivated after doing all the dry-run work. The deactivation is not expected, it is a result of a $srcdir/Makefile not existing, but the debugger does not pause the Extension Development Host when the deactivate() method is called. Instead, the Extension Development Host quickly reloads before I have a chance to examine the callstack. The callstack is of course cleared when the Host reloads. There must be a way to diagnose exactly why deactivate() is called, but I don't know how.
- Loading branch information
Showing
1 changed file
with
64 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters