[Audacity-devel] building the modules

mod-track-panel is obsolete. Does not need to be maintained.

It was little more than a copy of the then TrackPanel, to show you could
'clone' and then modify code. At one time the thought was that major
refactoring could be done in mod-track-panel. Instead we'll do it in main.

It is vital to maintain mod-null. It should do nothing - other than
show the minimum needed for a module.

Instructions on using mod-script-pipe are in the manual.

--James.

Post by Paul Licameli
Thank you Leland for updating xcode projects for the modules. I have not
tried to build them yet.
I tried on Windows. I can build the Visual Studio project for
mod-script-pipe with no problem. (I don't know yet what I do with it.)
I get some errors building mod-nyquist which are consequences of things I
did to CommandManager.h last year. I could work on fixing them.
I can't build mod-null. I can't build mod-track-panel. Are these
important to maintain or are they obsolete?
PRL
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Leland (Audacity Team)

2016-10-01 19:33:27 UTC

Post by Paul Licameli
I get some errors building mod-nyquist which are consequences of things I
did to CommandManager.h last year. I could work on fixing them.

Paul Licameli

2016-10-01 20:02:13 UTC

I see that this compiles, but makes a memory leak of gBench. The use of
SetCurrentMenu and ClearCurrent menu may "work" but are a little weird. I
don't know how to exercise it. Did you?

PRL

On Sat, Oct 1, 2016 at 3:33 PM, Leland (Audacity Team) <

Post by Paul Licameli
I get some errors building mod-nyquist which are consequences of things I
did to CommandManager.h last year. I could work on fixing them.

Just committed some changes that gets NyqBench working again. But, you may
want to review the changes to CommandManager since they may not follow your
design...update as appropriate.
Working on mod_null...
--
View this message in context: http://audacity.238276.n2.
nabble.com/building-the-modules-tp7576256p7576261.html
Sent from the audacity-devel mailing list archive at Nabble.com.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Leland (Audacity Team)

2016-10-01 21:08:00 UTC

Post by Paul Licameli
I see that this compiles, but makes a memory leak of gBench. The use of
SetCurrentMenu and ClearCurrent menu may "work" but are a little weird. I
don't know how to exercise it. Did you?

As mentioned, correct as you see fit. I just set out to get it building
again. Must get back to my 2nd job, though I will get mod_null working.

To try it out, build it (it will build into win/Debug/modules) and then go
into Preferences -> Modules and change it to enabled. Restart Audacity and
it should show up on the View menu.

The purpose of SetCurrentMenu/ClearCurrentMenu is simply to all the modules
to add a menu item on any of the existing menus or an entirely new menu.
Feel free to rework to fit into all of your new c++ stuff.

--
View this message in context: http://audacity.238276.n2.nabble.com/building-the-modules-tp7576256p7576264.html
Sent from the audacity-devel mailing list archive at Nabble.com.

Leland Lucius

2016-10-01 21:48:36 UTC

Post by Leland (Audacity Team)
As mentioned, correct as you see fit. I just set out to get it building

again.

Post by Leland (Audacity Team)
Must get back to my 2nd job, though I will get mod_null working.

Mod_null is building and working again (look on the Analyze menu for it's
items).

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Gale Andrews

2016-10-02 01:19:47 UTC

Hi Leland

Mod-script-pipe and mod-nyq-bench build for me on Windows 10, VS 2013
at "01eb474" "Get mod-null building again" but mod-null does not:

1>------ Rebuild All started: Project: mod-null, Configuration: Debug
Win32 ------
1> ModNullCallback.cpp
1>c:\git master\audacity\lib-src\mod-null\modnullcallback.cpp(121):
error C2065: 'ModuleDispatchTypes' : undeclared identifier
1>c:\git master\audacity\lib-src\mod-null\modnullcallback.cpp(121):
error C2146: syntax error : missing ')' before identifier 'type'
1>c:\git master\audacity\lib-src\mod-null\modnullcallback.cpp(121):
error C2059: syntax error : ')'
1>c:\git master\audacity\lib-src\mod-null\modnullcallback.cpp(122):
error C2143: syntax error : missing ';' before '{'
1>c:\git master\audacity\lib-src\mod-null\modnullcallback.cpp(122):
error C2447: '{' : missing function header (old-style formal list?)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped

I have the same error with debug configuration.

Gale

Post by Leland (Audacity Team)
As mentioned, correct as you see fit. I just set out to get it building

again.

Post by Leland (Audacity Team)
Must get back to my 2nd job, though I will get mod_null working.

Mod_null is building and working again (look on the Analyze menu for it's
items).
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Leland Lucius

2016-10-02 01:23:51 UTC

Oops...didn't commit the whole thing...sorry about that.

Committed now.

-----Original Message-----
Sent: Saturday, October 1, 2016 8:20 PM
Subject: Re: [Audacity-devel] building the modules
Hi Leland
Mod-script-pipe and mod-nyq-bench build for me on Windows 10, VS 2013 at
1>------ Rebuild All started: Project: mod-null, Configuration: Debug
Win32 ------
1> ModNullCallback.cpp
error C2065: 'ModuleDispatchTypes' : undeclared identifier
error C2146: syntax error : missing ')' before identifier 'type'
error C2059: syntax error : ')'
error C2143: syntax error : missing ';' before '{'
error C2447: '{' : missing function header (old-style formal list?)

==========

Rebuild All: 0 succeeded, 1 failed, 0 skipped
I have the same error with debug configuration.
Gale

Post by Leland (Audacity Team)
As mentioned, correct as you see fit. I just set out to get it building

again.

Post by Leland (Audacity Team)
Must get back to my 2nd job, though I will get mod_null working.

Mod_null is building and working again (look on the Analyze menu for
it's items).
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

----------------------------------------------------------------------------
--

Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Paul Licameli

2016-10-02 13:34:48 UTC

Is the Xcode project set up to build the modules from the graphical
interrace? I see mod-nyq-bench listed in the "targets" and I do find its
source code files in the project browser, but it must not have been
building for me, otherwise I would have known weeks ago that I had broken
it. If there is a way to switch the "target" I have not figured it out.

I will soon push source code changes in CommandManager.* that satisfy me
better.

PRL

Post by Leland Lucius
Oops...didn't commit the whole thing...sorry about that.
Committed now.

==========

Rebuild All: 0 succeeded, 1 failed, 0 skipped
I have the same error with debug configuration.
Gale

Post by Leland (Audacity Team)
As mentioned, correct as you see fit. I just set out to get it building

again.

Post by Leland (Audacity Team)
Must get back to my 2nd job, though I will get mod_null working.

Mod_null is building and working again (look on the Analyze menu for
it's items).
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------
----------------
--

Leland

2016-10-02 16:47:03 UTC

Sorry, I donât use the GUI for Xcode, so I never really thought about it much.

Iâve just committed new schemes, so you can now select the desired scheme from the toolbar or the âProductâ menu.

From: Paul Licameli [mailto:***@gmail.com]
Sent: Sunday, October 2, 2016 8:35 AM
To: Audacity-Devel list <audacity-***@lists.sourceforge.net>
Subject: Re: [Audacity-devel] building the modules

Is the Xcode project set up to build the modules from the graphical interrace? I see mod-nyq-bench listed in the "targets" and I do find its source code files in the project browser, but it must not have been building for me, otherwise I would have known weeks ago that I had broken it. If there is a way to switch the "target" I have not figured it out.

I will soon push source code changes in CommandManager.* that satisfy me better.

PRL

On Sat, Oct 1, 2016 at 9:23 PM, Leland Lucius <***@homerow.net <mailto:***@homerow.net> > wrote:

Oops...didn't commit the whole thing...sorry about that.

Committed now.

==========

Rebuild All: 0 succeeded, 1 failed, 0 skipped
I have the same error with debug configuration.
Gale

Post by Leland (Audacity Team)
As mentioned, correct as you see fit. I just set out to get it building

again.

Post by Leland (Audacity Team)
Must get back to my 2nd job, though I will get mod_null working.

Mod_null is building and working again (look on the Analyze menu for
it's items).
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

----------------------------------------------------------------------------
--

Gale Andrews

2016-10-02 18:40:33 UTC

The xcodebuild commands still work fine such as

xcodebuild -configuration Release install -target mod-nyq-bench .

Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe
or mod-nyq-bench in Product > Scheme. It usually takes multiple
reopening of the menu (or actually building the module) before
the checkmark will update to show the currently selected scheme.

I assume you saw the two warnings when building mod-script-pipe
on Mac, Leland?

/Users/gale/git/audacity/lib-src/mod-script-pipe/ScripterCallback.cpp:75:11:
ISO C++11 does not allow conversion from string literal to 'wxChar *' (aka
'wchar_t *')

/Users/gale/git/audacity/lib-src/mod-script-pipe/ScripterCallback.cpp:62:9:
'visibility' attribute ignored

There is no mod-null target on Mac. Should there not be so?

Thanks,

Gale

Post by Leland
Sorry, I donât use the GUI for Xcode, so I never really thought about it much.
Iâve just committed new schemes, so you can now select the desired scheme
from the toolbar or the âProductâ menu.
*Sent:* Sunday, October 2, 2016 8:35 AM
*Subject:* Re: [Audacity-devel] building the modules
Is the Xcode project set up to build the modules from the graphical
interrace? I see mod-nyq-bench listed in the "targets" and I do find its
source code files in the project browser, but it must not have been
building for me, otherwise I would have known weeks ago that I had broken
it. If there is a way to switch the "target" I have not figured it out.
I will soon push source code changes in CommandManager.* that satisfy me better.
PRL
Oops...didn't commit the whole thing...sorry about that.
Committed now.

==========

Rebuild All: 0 succeeded, 1 failed, 0 skipped
I have the same error with debug configuration.
Gale

Post by Leland (Audacity Team)
As mentioned, correct as you see fit. I just set out to get it building

again.

Post by Leland (Audacity Team)
Must get back to my 2nd job, though I will get mod_null working.

Mod_null is building and working again (look on the Analyze menu for
it's items).
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------
----------------
--

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
<https://www.avast.com/en-us/lp-safe-emailing-2270-a?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2270-a> Virus-free.
www.avast.com
<https://www.avast.com/en-us/lp-safe-emailing-2270-a?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2270-a>
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Leland

2016-10-02 19:44:41 UTC

-----Original Message-----
Sent: Sunday, October 2, 2016 1:41 PM
Subject: Re: [Audacity-devel] building the modules
The xcodebuild commands still work fine such as
xcodebuild -configuration Release install -target mod-nyq-bench .
Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe or mod-
nyq-bench in Product > Scheme. It usually takes multiple reopening of the
menu (or actually building the module) before the checkmark will update to
show the currently selected scheme.

I "think" it still switches even though the checkmark doesn't update. (command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on Mac,
Leland?

Noper.

There is no mod-null target on Mac. Should there
not be so?

Steve the Fiddle

2016-10-02 19:55:52 UTC

I'm still having no joy on Linux. Has anyone succeeded building
modules on Linux?

Steve

I "think" it still switches even though the checkmark doesn't update. (command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on Mac,
Leland?

Noper.

There is no mod-null target on Mac. Should there
not be so?

I s'pose. I just thought any "testing" of it could be done on Windows. But, I've just added it to the project.
Leland
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Leland Lucius

2016-10-03 00:21:12 UTC

Try it now

-----Original Message-----
Sent: Sunday, October 2, 2016 2:56 PM
Subject: Re: [Audacity-devel] building the modules
I'm still having no joy on Linux. Has anyone succeeded building modules on
Linux?
Steve

-----Original Message-----
Sent: Sunday, October 2, 2016 1:41 PM
Subject: Re: [Audacity-devel] building the modules
The xcodebuild commands still work fine such as
xcodebuild -configuration Release install -target mod-nyq-bench .
Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe
or mod- nyq-bench in Product > Scheme. It usually takes multiple
reopening of the menu (or actually building the module) before the
checkmark will update to show the currently selected scheme.

I "think" it still switches even though the checkmark doesn't update.
(command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on
Mac, Leland?

Noper.

There is no mod-null target on Mac. Should there not be so?

I s'pose. I just thought any "testing" of it could be done on Windows.

But,

I've just added it to the project.

Post by Leland
Leland
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

----------------------------------------------------------------------------
--

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Steve the Fiddle

2016-10-03 13:00:13 UTC

Thanks Leland.

I've only tested Nyquist Workbench. It has built and is working.

Steve

Post by Leland Lucius
Try it now

-----Original Message-----
Sent: Sunday, October 2, 2016 1:41 PM
Subject: Re: [Audacity-devel] building the modules
The xcodebuild commands still work fine such as
xcodebuild -configuration Release install -target mod-nyq-bench .
Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe
or mod- nyq-bench in Product > Scheme. It usually takes multiple
reopening of the menu (or actually building the module) before the
checkmark will update to show the currently selected scheme.

I "think" it still switches even though the checkmark doesn't update.
(command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on
Mac, Leland?

Noper.

There is no mod-null target on Mac. Should there not be so?

I s'pose. I just thought any "testing" of it could be done on Windows.

But,

I've just added it to the project.

----------------------------------------------------------------------------
--

Gale Andrews

2016-10-03 16:04:49 UTC

Post by Steve the Fiddle
Thanks Leland.
I've only tested Nyquist Workbench. It has built and is working.
Steve

I don't have it working yet on Ubuntu 14.04 32-bit, but I don't know
whether that it is because I build Audacity in a "build" folder as is
often recommended.

Following
http://wiki.audacityteam.org/wiki/Nyquist_Plug-ins_Reference#Nyquist_Workbench

still works for me if I perform those steps in
audacity/build/lib-src/mod-nyq-bench (I corrected the copy command
there for copying the modules to /usr/local/share/audacity/modules).

But if after building Audacity in the "build" folder I try to build
mod-nyq-bench in audacity/lib-src/mod-nyq-bench, then after "make", it
says "no targets specified and no makefile found". If I ./configure in
that mod-nyq-bench folder then make, I get

"in file included from NyqBench.cpp:9:0:
./../../src/Audacity.h:85:24 fatal error: configunix.h: no such file
or directory".

Same with audacity/lib-src/mod-script-pipe. The "build" folder does
not have a "mod-script-pipe" folder.

Does someone have more up-to-date instructions, both using a "build"
folder to build Audacity and not? The Wiki instructions are l fine for
Windows and Mac, with a few tweaks for Mac I made yesterday.

Gale

Post by Leland Lucius
Try it now

-----Original Message-----
Sent: Sunday, October 2, 2016 1:41 PM
Subject: Re: [Audacity-devel] building the modules
The xcodebuild commands still work fine such as
xcodebuild -configuration Release install -target mod-nyq-bench .
Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe
or mod- nyq-bench in Product > Scheme. It usually takes multiple
reopening of the menu (or actually building the module) before the
checkmark will update to show the currently selected scheme.

I "think" it still switches even though the checkmark doesn't update.
(command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on
Mac, Leland?

Noper.

There is no mod-null target on Mac. Should there not be so?

I s'pose. I just thought any "testing" of it could be done on Windows.

But,

I've just added it to the project.

----------------------------------------------------------------------------
--

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Steve the Fiddle

2016-10-03 20:03:52 UTC

It took me a couple of goes to get it to work.
It's probably easiest to delete the entire audacity folder and start
with a fresh clone, but if you don't want to do that:

1) Delete your "build" folder.
2) Run "make distclean" in the src directory (may be necessary if you
have previously run ./configure there).
3) Run "make distclean" in the lib-src/mod-nyq-bench/ folder (may be
necessary if you have previously attempted building the module).

You should now be able to build in a new "build" directory, but ensure
that you have plenty of time before midnight otherwise the module
turns into a pumpkin.

4) mkdir build
5) cd build
6) ../configure <options>
I used:
../configure --disable-dynamic-loading --enable-debug

7) make
Audacity should build correctly.

8) cd lib-src/mod-nyq-bench
This directory should now exist.

9) make
This should complete without errors (though there will probably be
some warnings).

There should now be a hidden folder:
/build/lib-src/mod-nyq-bench/.libs
containing three files and three links.

10) cd ../../..
to get back to the root of the source tree

11) mkdir modules
to create a modules directory

12) copy the file "mod-nyq-bench.so.0.0.0" and the link
"mod-nyq-bench.so" from the
/build/lib-src/mod-nyq-bench/.libs
directory into the new "modules" directory.

13) Launch Audacity
14) Enable Nyquist Workbench in "Preferences > Modules"
15) Restart Audacity.

Good luck.

Steve

Post by Steve the Fiddle
Thanks Leland.
I've only tested Nyquist Workbench. It has built and is working.
Steve

I don't have it working yet on Ubuntu 14.04 32-bit, but I don't know
whether that it is because I build Audacity in a "build" folder as is
often recommended.
Following
http://wiki.audacityteam.org/wiki/Nyquist_Plug-ins_Reference#Nyquist_Workbench
still works for me if I perform those steps in
audacity/build/lib-src/mod-nyq-bench (I corrected the copy command
there for copying the modules to /usr/local/share/audacity/modules).
But if after building Audacity in the "build" folder I try to build
mod-nyq-bench in audacity/lib-src/mod-nyq-bench, then after "make", it
says "no targets specified and no makefile found". If I ./configure in
that mod-nyq-bench folder then make, I get
./../../src/Audacity.h:85:24 fatal error: configunix.h: no such file
or directory".
Same with audacity/lib-src/mod-script-pipe. The "build" folder does
not have a "mod-script-pipe" folder.
Does someone have more up-to-date instructions, both using a "build"
folder to build Audacity and not? The Wiki instructions are l fine for
Windows and Mac, with a few tweaks for Mac I made yesterday.
Gale

Post by Leland Lucius
Try it now

-----Original Message-----
Sent: Sunday, October 2, 2016 1:41 PM
Subject: Re: [Audacity-devel] building the modules
The xcodebuild commands still work fine such as
xcodebuild -configuration Release install -target mod-nyq-bench .
Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe
or mod- nyq-bench in Product > Scheme. It usually takes multiple
reopening of the menu (or actually building the module) before the
checkmark will update to show the currently selected scheme.

I "think" it still switches even though the checkmark doesn't update.
(command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on
Mac, Leland?

Noper.

There is no mod-null target on Mac. Should there not be so?

I s'pose. I just thought any "testing" of it could be done on Windows.

But,

I've just added it to the project.

----------------------------------------------------------------------------
--

James Crook

2016-10-03 21:49:00 UTC

Post by Steve the Fiddle
It took me a couple of goes to get it to work.
It's probably easiest to delete the entire audacity folder and start
1) Delete your "build" folder.
2) Run "make distclean" in the src directory (may be necessary if you
have previously run ./configure there).
3) Run "make distclean" in the lib-src/mod-nyq-bench/ folder (may be
necessary if you have previously attempted building the module).
You should now be able to build in a new "build" directory, but ensure
that you have plenty of time before midnight otherwise the module
turns into a pumpkin.

Myself and Paul can vouch for the truth of that. Here's a photo:

Module and Audacity must be built on the same day. If the build crosses
midnight the dates don't match up, so that build of that module is not
compatible with that build of Audacity.

--James.

Gale Andrews

2016-10-04 22:29:04 UTC

It now takes 90 minutes to build Audacity on my Ubuntu netbook so I
got the pumpkin. That started about the time changes were made to
speed Windows builds up.

Anyway, results for Ubuntu below.

Post by Steve the Fiddle
4) mkdir build
5) cd build
6) ../configure <options>
../configure --disable-dynamic-loading --enable-debug
7) make
Audacity should build correctly.
8) cd lib-src/mod-nyq-bench
This directory should now exist.
9) make
This should complete without errors (though there will probably be
some warnings).
/build/lib-src/mod-nyq-bench/.libs
containing three files and three links.
10) cd ../../..
to get back to the root of the source tree
11) mkdir modules
to create a modules directory
12) copy the file "mod-nyq-bench.so.0.0.0" and the link
"mod-nyq-bench.so" from the
/build/lib-src/mod-nyq-bench/.libs
directory into the new "modules" directory.
13) Launch Audacity
14) Enable Nyquist Workbench in "Preferences > Modules"
15) Restart Audacity.

Mod-nyq-bench built OK following those steps, but then it built before
for me if I built in /build/lib-src/mod-nyq-bench. The problem was
trying to then build the modules in <root of
source>/lib-src/mod-nyq-bench or /mod-script-pipe - there is no target
for make until you configure, and when you make after configure you
get "configunix.h: no such file or directory".

Having built Audacity in the "build" folder with your steps, Audacity
refuses to see the modules in <root of source>/modules. It sees them
in a "modules" folder inside the "build" folder - I've tried a couple
of times. Does a "modules" folder inside the "build" folder also work
for you, so we can document that?

Then I did a fresh checkout and built Audacity in the root of source.
Building mod-nyq-bench in lib-src (just with "make") went fine and
Audacity saw mod-nyq-bench in <root of source>/modules.

But there is no makefile for mod-null (if we care) and building
mod-script pipe fails thus:

/usr/local/include/wx-3.0/wx/chartype.h:296:23: note: in expansion of
macro 'wxAPPLY_T'
#define __TDATE__ wxAPPLY_T(__DATE__)
^
../../src/Audacity.h:39:43: note: in expansion of macro '__TDATE__'
#define AUDACITY_SUFFIX wxT("-alpha-") __TDATE__
^
../../src/Audacity.h:51:33: note: in expansion of macro 'AUDACITY_SUFFIX'
AUDACITY_SUFFIX
^
ScripterCallback.cpp:75:11: note: in expansion of macro
'AUDACITY_VERSION_STRING'
return AUDACITY_VERSION_STRING;
^
make: *** [ScripterCallback.o] Error 1

So AFAICT mod-script-pipe can't be attempted when building Audacity in
a "build" folder, and when you don't use a "build" folder
mod-script-pipe does not build properly.

Gale

Post by Steve the Fiddle
Good luck.
Steve

Post by Steve the Fiddle
Thanks Leland.
I've only tested Nyquist Workbench. It has built and is working.
Steve

I don't have it working yet on Ubuntu 14.04 32-bit, but I don't know
whether that it is because I build Audacity in a "build" folder as is
often recommended.
Following
http://wiki.audacityteam.org/wiki/Nyquist_Plug-ins_Reference#Nyquist_Workbench
still works for me if I perform those steps in
audacity/build/lib-src/mod-nyq-bench (I corrected the copy command
there for copying the modules to /usr/local/share/audacity/modules).
But if after building Audacity in the "build" folder I try to build
mod-nyq-bench in audacity/lib-src/mod-nyq-bench, then after "make", it
says "no targets specified and no makefile found". If I ./configure in
that mod-nyq-bench folder then make, I get
./../../src/Audacity.h:85:24 fatal error: configunix.h: no such file
or directory".
Same with audacity/lib-src/mod-script-pipe. The "build" folder does
not have a "mod-script-pipe" folder.
Does someone have more up-to-date instructions, both using a "build"
folder to build Audacity and not? The Wiki instructions are l fine for
Windows and Mac, with a few tweaks for Mac I made yesterday.
Gale

Post by Leland Lucius
Try it now

-----Original Message-----
Sent: Sunday, October 2, 2016 1:41 PM
Subject: Re: [Audacity-devel] building the modules
The xcodebuild commands still work fine such as
xcodebuild -configuration Release install -target mod-nyq-bench .
Xcode 7.1 on Sierra is really buggy when you select mod-script-pipe
or mod- nyq-bench in Product > Scheme. It usually takes multiple
reopening of the menu (or actually building the module) before the
checkmark will update to show the currently selected scheme.

I "think" it still switches even though the checkmark doesn't update.
(command line is SO much better. :-D)

I assume you saw the two warnings when building mod-script-pipe on
Mac, Leland?

Noper.

There is no mod-null target on Mac. Should there not be so?

I s'pose. I just thought any "testing" of it could be done on Windows.

But,

I've just added it to the project.

----------------------------------------------------------------------------
--

Gale Andrews

2016-10-19 00:53:04 UTC

It now takes 90 minutes to build Audacity on my Ubuntu netbook so I
got the pumpkin. That started about the time changes were made to
speed Windows builds up.
Anyway, results for Ubuntu below.

Given that is the only method that works for me, I documented it:
http://wiki.audacityteam.org/wiki/Nyquist_Plug-ins_Reference#GNU.2FLinux .

Gale

Post by Gale Andrews
Then I did a fresh checkout and built Audacity in the root of source.
Building mod-nyq-bench in lib-src (just with "make") went fine and
Audacity saw mod-nyq-bench in <root of source>/modules.
But there is no makefile for mod-null (if we care) and building
/usr/local/include/wx-3.0/wx/chartype.h:296:23: note: in expansion of
macro 'wxAPPLY_T'
#define __TDATE__ wxAPPLY_T(__DATE__)
^
../../src/Audacity.h:39:43: note: in expansion of macro '__TDATE__'
#define AUDACITY_SUFFIX wxT("-alpha-") __TDATE__
^
../../src/Audacity.h:51:33: note: in expansion of macro 'AUDACITY_SUFFIX'
AUDACITY_SUFFIX
^
ScripterCallback.cpp:75:11: note: in expansion of macro
'AUDACITY_VERSION_STRING'
return AUDACITY_VERSION_STRING;
^
make: *** [ScripterCallback.o] Error 1
So AFAICT mod-script-pipe can't be attempted when building Audacity in
a "build" folder, and when you don't use a "build" folder
mod-script-pipe does not build properly.
Gale

Post by Steve the Fiddle
Good luck.
Steve

Post by Steve the Fiddle
Thanks Leland.
I've only tested Nyquist Workbench. It has built and is working.
Steve

I don't have it working yet on Ubuntu 14.04 32-bit, but I don't know
whether that it is because I build Audacity in a "build" folder as is
often recommended.
Following
http://wiki.audacityteam.org/wiki/Nyquist_Plug-ins_Reference#Nyquist_Workbench
still works for me if I perform those steps in
audacity/build/lib-src/mod-nyq-bench (I corrected the copy command
there for copying the modules to /usr/local/share/audacity/modules).
But if after building Audacity in the "build" folder I try to build
mod-nyq-bench in audacity/lib-src/mod-nyq-bench, then after "make", it
says "no targets specified and no makefile found". If I ./configure in
that mod-nyq-bench folder then make, I get
./../../src/Audacity.h:85:24 fatal error: configunix.h: no such file
or directory".
Same with audacity/lib-src/mod-script-pipe. The "build" folder does
not have a "mod-script-pipe" folder.
Does someone have more up-to-date instructions, both using a "build"
folder to build Audacity and not? The Wiki instructions are l fine for
Windows and Mac, with a few tweaks for Mac I made yesterday.
Gale

Post by Leland Lucius
Try it now