xCode
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
 |
xCode
by Brian-14
::
Rate this Message:
http://portaudio.com/docs/pa_tut_mac_osx.html
I am trying to use XCode for working with portaudio. I guess that is what is meant by "ProjectBuilder" at the link above. Everything seems OK, but I cannot follow the last line. Compile and run the "pa_tests:patest_saw.c" file first because it is the simplest. I selected the patest_saw.c in the "Source" part of the project and then did a "compile" no error messages, but how to "run" it? Anybody out there who could give me a hand with this. Brian |
|
|
Re: xCode
by paul-20
::
Rate this Message:
I understand that you need to link the compiled test code to the
portaudio library to create an executable binary and then run this. If
it does the intended tasks (check doc and source code) then the test
passed.
Paul Brian wrote on 7/7/2005 11:33 AM: http://portaudio.com/docs/pa_tut_mac_osx.html |
|
|
Re: xCode
by Richard Dobson
::
Rate this Message:
The test programs are command-line - you run them from Terminal. resistance is
futile...:-) Richard Dobson paul wrote: > I understand that you need to link the compiled test code to the > portaudio library to create an executable binary and then run this. If > it does the intended tasks (check doc and source code) then the test passed. > Paul > > Brian wrote on 7/7/2005 11:33 AM: > >> http://portaudio.com/docs/pa_tut_mac_osx.html >> >> I am trying to use XCode for working with portaudio. I guess that is >> what is meant by "ProjectBuilder" at the link above. >> >> Everything seems OK, but I cannot follow the last line. >> >> Compile and run the "pa_tests:patest_saw.c" file first because it is >> the simplest. >> >> I selected the patest_saw.c in the "Source" part of the project and >> then did a "compile" no error messages, but how to "run" it? >> >> Anybody out there who could give me a hand with this. >> >> Brian > _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: xCode
by leeNZ
::
Rate this Message:
Hi,
I have successfully compiled the sawtooth example using the portAudio v19 snapshot, and xCode 2.4.1. However I am having issues with linking. At first I got this error at runtime: dyld: Library not loaded: /usr/local/lib/libportaudio.2.dylib Referenced from: /code/xcode/soundTest2/build/Release/ ...which I fixed by manually copying libportaudio.2.dylib to /usr/local/lib/ using the terminal. I have linked the project to libportaudio.a, which I was under the impression was for static linking, so why does the program depend on this dynamic library? Can anyone help me to link this statically? I am quite new to xCode, so I may be missing something obvious... Another issue I have is that I can only compile in release mode. If I try debug mode I get the following error: ZeroLink: unknown symbol '_FindNextComponent' soundTest2 has exited due to signal 6 (SIGABRT). ...which suggests again that I may be linking incorrectly?? Some additional information: my project is a c++ commandline app. I "converted" the sawtooth code from .c to .cpp. (fixing main() to accept the right arguments) I have not included any mac audio frameworks, and the example works without them, just using libportaudio.a and portaudio.h. Thanks. |
|
|
|
|
|
Re: xCode
by Brenton Partridge
::
Rate this Message:
Hi,
On Dec 7, 2007, at 7:23 PM, Bjorn Roche wrote: > Woops, forgot to send this to the list... > > Lee, > > First thing I would recommend is uninstalling the dynamic library > if possible, to make sure you are not accidentally referencing it. > Then add the .a file, as I believe you already have, and make sure > you've included all the necessary frameworks as listed in the > tutorial. The error message you give suggests that you have not > included CoreServices in your project and CoreServices, along with > several other frameworks, is listed in the tutorial as being > required to get PortAudio working in X Code. Perhaps there is > something wrong with the way you've linked CoreServices that won't > let it link in debug? I haven't tried in a while, but I've found that ZeroLink doesn't work really well with the audio frameworks - probably an oversight on my part, but if you need debug symbols and stuff, try just disabling ZeroLink. Brenton > maybe just try removing it and readding it? I hope that's enough of > a hint anyway. If not, you could also try asking on apple's xcode > mailing list. > > bjorn > > no further comments follow. > > On Dec 4, 2007, at 6:48 PM, leeNZ wrote: > >> >> Hi, >> >> I have successfully compiled the sawtooth example using the >> portAudio v19 >> snapshot, and xCode 2.4.1. However I am having issues with linking. >> >> At first I got this error at runtime: >> >> dyld: Library not loaded: /usr/local/lib/libportaudio.2.dylib >> Referenced from: /code/xcode/soundTest2/build/Release/ >> >> ...which I fixed by manually copying libportaudio.2.dylib to /usr/ >> local/lib/ >> using the terminal. >> I have linked the project to libportaudio.a, which I was under the >> impression was for static linking, so why does the program depend >> on this >> dynamic library? Can anyone help me to link this statically? I am >> quite new >> to xCode, so I may be missing something obvious... >> >> Another issue I have is that I can only compile in release mode. >> If I try >> debug mode I get the following error: >> >> ZeroLink: unknown symbol '_FindNextComponent' >> soundTest2 has exited due to signal 6 (SIGABRT). >> >> ...which suggests again that I may be linking incorrectly?? >> >> Some additional information: my project is a c++ commandline app. I >> "converted" the sawtooth code from .c to .cpp. (fixing main() to >> accept the >> right arguments) I have not included any mac audio frameworks, and >> the >> example works without them, just using libportaudio.a and >> portaudio.h. >> >> Thanks. >> >> -- >> View this message in context: http://www.nabble.com/xCode- >> tf128140.html#a14162193 >> Sent from the Portaudio - Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> Portaudio mailing list >> Portaudio@... >> http://techweb.rfa.org/mailman/listinfo/portaudio > > ----------------------------- > Bjorn Roche > XO Wave > Digital Audio Production and Post-Production Software > http://www.xowave.com > http://blog.bjornroche.com > http://myspace.com/xowave > _______________________________________________ > Portaudio mailing list > Portaudio@... > http://techweb.rfa.org/mailman/listinfo/portaudio _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: xCode
by zencuke
::
Rate this Message:
I am not able to compile the sawtooth, probably because I am new to xcode and didn't create the correct projects type (so many choices, so little explanation.)
My xcode project type is "command line utility" -> "C++ tool." That seemed reasonable at the time. I was not able to exactly follow the instructions in the tutorial because the project does not have an External Frameworks and Libraries" group. I added the portaudio library at the top instead and then can't compile because #include "pa_common/portaudio.h" is not found. I don't know the xcode project equivalent of -I on the gcc line. What am I doing wrong? As a general comment I found the macintosh compile and build instructions to be a little too terse for someone with my apparently massive level of ignorance. I had never used the "open" command for example and initially couldn't figure out where I was supposed to "enter" it. Thinking it was an xcode thinggy I was looking for an xcode console to type it into. I eventually figured out that I could do it in bash. The documentation could have said that (by adding the words "at a shell prompt") and saved me some time. The doc about xcode assumes that you are still in the directory that "./configure/; make" left you. It would be nice if it said so. When things go wrong you wonder about things like that. I suggest that just a few more lines of clarification in the Macintosh build page would have made these things unambiguous even to a total xcode beginner and I wouldn't be wasting this list's time asking for help on what must be an obvious problem. I've been a UNIX hacker since it was ported from various PDPs to the 68000 (one of those ports was mine) and have used gcc almost as long as it has existed (some of my optimizations went into early versions.) I've been away from mac development for quite a while (pre PowerPC) but wrote my first mac app when the only native development environment was MacForth. Mostly this just proves that I'm old, living on past glories and probably going senile but I'm clearly not a beginner. Normally I don't have this much difficulty picking up a new tool in a new environment. When someone answers my question I propose that some consideration should be made to adding that info to the mac tutorial as well as my suggestions above. Best regards Steve Morris (zencuke) |
|
|
Re: xCode
by Bjorn Roche
::
Rate this Message:
On May 11, 2008, at 11:43 PM, zencuke wrote: > > I am not able to compile the sawtooth, probably because I am new to > xcode > and didn't create the correct projects type (so many choices, so > little > explanation.) I'm not sure exactly what you mean. patest_saw.c, perhaps? That compiles when you compile the library by following the instructions in the tutorial. If you want to make an XCode project out of it, I imagine you'll have to make some changes, and doing so will mean understanding how XCode works, which, despite the fact that it's built on gnu tools, is different from make. Theoretically we could explain everything in the tutorial, but there are two problems: once the tutorial gets too long, people start to miss the critical points, and the tutorial is not the place for instructions that are IDE-specific and say things like "select such and such from the foo menu" which could depend on your project type and could change depending on your IDE version. I'm afraid that for the time being it's up to you to understand the IDE, since our job is to provide the library and your job is to use it as you would any other library, but I'll try to offer some suggestions. Perhaps someone with more XCode experience can offer more (accurate) advice. > My xcode project type is "command line utility" -> "C++ tool." That > seemed > reasonable at the time. > > I was not able to exactly follow the instructions in the tutorial > because > the project does not have an External Frameworks and Libraries" > group. I > added the portaudio library at the top instead and then can't compile > because > > #include "pa_common/portaudio.h" > > is not found. I don't know the xcode project equivalent of -I on the > gcc > line. > > What am I doing wrong? Unless you have a pa_common folder in your XCode project, I suspect that's not place for it to look. you should probably change the include line to be simply #include "portaudio.h" As for adding the library (.a) and header files (.h), there is a contextual menu: right click on the top level file and select add:existing file... and you should be able to add both the .h and the .a files that way, though I'm not sure if that's the best way, since I don't really work in XCode. I hope that helps. bjorn ----------------------------- Bjorn Roche XO Wave Digital Audio Production and Post-Production Software http://www.xowave.com http://blog.bjornroche.com http://myspace.com/xowave _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: xCode
by Bjorn Roche
::
Rate this Message:
On May 11, 2008, at 11:43 PM, zencuke wrote: > > As a general comment I found the macintosh compile and build > instructions to > be a little too terse for someone with my apparently massive level of > ignorance. I had never used the "open" command for example and > initially > couldn't figure out where I was supposed to "enter" it. Thinking it > was an > xcode thinggy I was looking for an xcode console to type it into. I > eventually figured out that I could do it in bash. The documentation > could > have said that (by adding the words "at a shell prompt") and saved > me some > time. The doc about xcode assumes that you are still in the > directory that > "./configure/; make" left you. It would be nice if it said so. When > things > go wrong you wonder about things like that. That's easy enough to fix, however, I'm not sure going into tremendous detail about XCode is a good idea for the reasons I mentioned in my previous email. Phil: I am having trouble logging on to trac. The connection just hangs when I try, but what's weird is it doesn't time out. bjorn ----------------------------- Bjorn Roche XO Wave Digital Audio Production and Post-Production Software http://www.xowave.com http://blog.bjornroche.com http://myspace.com/xowave _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
|
|
|
Re: xCode
by zencuke
::
Rate this Message:
Below is the wiki macintosh tutorial page I am commenting on that I find somewhat ambiguous and just a little too terse. The changes I propose for this page are:1) Define the root directory for all the file/directory references. A commonly used syntax is something like: <port audio build area>/lib/. This can be figured out by reading the previous section but why not be explicit. Then the section can stand alone if the user jumps straight there. 2) Specify one or more project types that can be used. "xcode project" is an ambiguous and overloaded expression. I didn't count but the project type list had roughly 40 choices. The list doesn't need to be complete. A single choice that will work with the demo is sufficient. For consistency it should be a type that has a "External Frameworks and Libraries" group since the instructions reference that group. Not all xcode project types do. 3) Specify where the "open" command should be "entered," i.e. at a shell prompt in the port audio build area. This was obvious in retrospect but was not so initially. http://www.portaudio.com/trac/wiki/TutorialDir/Compile/MacintoshCoreAudio Using the Library in XCode Projects ΒΆOnce your compilation completes, the easiest and recommended way to use PortAudio in your X Code project is to add "pa_common/portaudio.h" and "lib/.libs/libportaudio.a" to your project. Note that "lib/.libs/" is a hidden directory, so you won't be able to navigate to "lib/.libs/libportaudio.a" using the finder or the standard Mac OS file dialogs. In order to add it to your XCode project, open the hidden folder by entering: $ open lib/.libs Then drag the "libportaudio.a" file into your XCode project and place it in the "External Frameworks and Libraries" group. You will need to add the following frameworks to your XCode project:
On Mon, May 12, 2008 at 1:50 PM, Bjorn Roche <bjorn@...> wrote: The tutorial says the same thing: _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Trac logins fixed?
by Phil Burk
::
Rate this Message:
> Phil: I am having trouble logging on to trac. The connection just > hangs when I try, but what's weird is it doesn't time out. I just get rejected. I added 'apache' user to the group that owns the password file for portaudio-trac and it seems to work now. Please give it a try. Phil Burk _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: Trac logins fixed?
by Bjorn Roche
::
Rate this Message:
On May 13, 2008, at 1:11 AM, Phil Burk wrote: > >> Phil: I am having trouble logging on to trac. The connection just >> hangs when I try, but what's weird is it doesn't time out. > > I just get rejected. I added 'apache' user to the group that owns the > password file for portaudio-trac and it seems to work now. > > Please give it a try. Great, I can log on to trac, but I can't svn ci (I can svn up): gogo:~/pa bjorn$ svn ci -m "removed obsolete darwin compiling instructions" svn: Commit failed (details follow): svn: Can't create directory '/home/svnroot/portaudio/db/transactions/ 1381-1.txn': Permission denied bjorn ----------------------------- Bjorn Roche XO Wave Digital Audio Production and Post-Production Software http://www.xowave.com http://blog.bjornroche.com http://myspace.com/xowave _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: xCode
by Bjorn Roche
::
Rate this Message:
Okay, I made some changes to clarify those points. Thanks for your
comments. bjorn On May 12, 2008, at 11:25 PM, Steve Morris wrote: > Below is the wiki macintosh tutorial page I am commenting on that I > find somewhat ambiguous and just a little too terse. The changes I > propose for this page are: > 1) Define the root directory for all the file/directory references. > A commonly used syntax is something like: > <port audio build area>/lib/. This can be figured out by reading the > previous section but why not be explicit. Then the section can stand > alone if the user jumps straight there. > > 2) Specify one or more project types that can be used. "xcode > project" is an ambiguous and overloaded expression. I didn't count > but the project type list had roughly 40 choices. The list doesn't > need to be complete. A single choice that will work with the demo is > sufficient. For consistency it should be a type that has a > "External Frameworks and Libraries" group since the instructions > reference that group. Not all xcode project types do. > > 3) Specify where the "open" command should be "entered," i.e. at a > shell prompt in the port audio build area. This was obvious in > retrospect but was not so initially. > > http://www.portaudio.com/trac/wiki/TutorialDir/Compile/MacintoshCoreAudio ----------------------------- Bjorn Roche XO Wave Digital Audio Production and Post-Production Software http://www.xowave.com http://blog.bjornroche.com http://myspace.com/xowave _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: xCode
by zencuke
::
Rate this Message:
Thank you. It looks good. Sorry to be a bother.
On Tue, May 13, 2008 at 9:00 AM, Bjorn Roche <bjorn@...> wrote: Okay, I made some changes to clarify those points. Thanks for your comments. -- Steve Morris barbershopsteve@... Bass: Unnamed quintet/quartet whatever Bass: Sounds Of Concord _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: Trac logins fixed?
by Phil Burk
::
Rate this Message:
> Great, I can log on to trac, but I can't svn ci (I can svn up): I just tried it and had the same problem. So I did a 'chmod -R g+w /home/svnroot/portaudio' and now I can do 'svn ci' Please let me know if that was not an appropriate fix. BTW, I was able to use the https: URL for svn so I think we have password encryption. The certificate is a funky test certificate provided by the web hosting provider. I will try to get a better certificate. Phil Burk _______________________________________________ Portaudio mailing list Portaudio@... http://techweb.rfa.org/mailman/listinfo/portaudio |
|
|
Re: Trac logins fixed?
by Bjorn Roche
::
Rate this Message:
On May 13, 2008, at 12:36 PM, Phil Burk wrote: > >> Great, I can log on to trac, but I can't svn ci (I can svn up): > > I just tried it and had the same problem. > > So I did a 'chmod -R g+w /home/svnroot/portaudio' &g |
