Fixes configure.sh
Fixes Windows code signing
Fixes an issue with conan cache on windows
Fixes build manual script
Fixes build manual
Remove unused props
Use long options
Yet another manual fix
Fixes iss
Break the workflow into smaller stages (Configure, Build, Install,
Package, etc.) so that you can see exactly which stage failed in the
GitHub Actions run log.
Create a separate Bash CI script for each job stage (configure.sh,
build.sh, install.sh, package.sh, etc.) to reduce the size of the main
YAML workflow file and enable Bash syntax highlighting.
Close#917
There are now extra blank lines in the results that
need to be dealt with. Script updated to do so.
This bug 2665 is now fixed. I think there is a small issue
with the label command not using the selection that
still needs to be addressed too, but it is minor compared
to bug 2665 and can wait.
The conversion from Python2 to Python3 had some issues.
- Characters outside the ASCII range got converted to \xe2\x80 numbers
- Single quotes got escaped.
- The entire doc was enclosed in quotes.
These changes address those, and also remove html comments.
This adds a new target that will build the "minsrc" tarball.
It can be created on any platform now, either from the command
line or from within the Window's and Mac's project files.
The output tarball will be in the build directory.
And it's very easy to update the list of files/directories to
exclude...see scripts/CMakeLists.txt
... Not the most satisfactory fix, but in fact no dangling pointers will
happen with the code we have now, because the relevant windows are all destroyed
only at the end of AudacityProject's lifetime, including the non-modal windows
(macros, history, lyrics, mixer board, plot spectrum, and contrast) which
are hidden and shown again, not destroyed and recreated, when dismissed and
reopened.
To do: figure out how to make wxWeakRef work on that combination without
crashing.
... To use it, first install graphViz. Then change to the scripts directory
and run ./graph.pl . Then view the resulting image file in a browser.
See an acyclic graph, each node labeled with the list of .cpp files in
one strongly connected component of the linkage dependencies as determined
by scanning the #include directives in the sources.
It worked for me in macOS.
