Search results

Yep. Apparantly you still have not added it to your project correctly. Notice that there's no -lncurses. That should definitely be there if it were in your project correctly. Delete libncurses.dylib from your project, use "Add Files to project", navigate to /usr/lib, add libncurses.dylib...

All you should have to do is choose Project->Add Files and add it to the project. Attempt a build and then choose "Show Detailed Build Results" from the build menu. At the bottom of the window is a little dimple. Drag that up to expose the command-line output. Copy and paste that...

That's a linker error. It's trying to find the code for that routine but can't. You need to add /usr/lib/libncurses.dylib to your project. Wade

No, I think they may have gotten hacked again. From what I understand, they're working on bringing up a new server now (on OS X this time). Wade

Before we go any further, what kind of Mac with what OS are you doing this on? Let's make sure MPW is an absolute requirement. Secondly, post your Makefile here. If we can see it, it will be much easier to describe what to do. Wade

I took a brief look at it. If you look at JKA_mp(SDK).sln, you'll see that it references all the .vcproj files. It's the master project file. The .vcproj files make up the individual modules. If you look in the .vcproj files, you'll see all the files that comprise the module. By looking...

Does he have a Linux version? If so, the Makefile and such would likely be convertible to OS X without too many changes. Wade

I don't know of anything that can open a Visual C++ project. You'll need to recreate it in your IDE of choice (CW or XCode). Wade

See: http://developer.apple.com/hardware/usb/index.html There's information on that page for loading debugging kernel extensions, using the USB prober application, how to write for IOKit, etc, etc. I think you'll find what you need there. Wade

Extend it to 1024 - really. It's 1,000 bytes. That's absolutely nothing and certainly worth it to ensure no path will overflow your buffer. I commend your desire to save memory but in this case, making sure the buffer is of sufficient size to handle the maximum allowable pathname is not...

Well, you do understand that it will fail if full_filename is more than 50 characters, right? You probably should make full_filename the length of a maximum allowable pathname, which I believe is defined as MAX_PATH and is 1024 bytes. Wade

With the aforementioned mode problem, that code should work on any OS X system. You'd have to be more specific about where it's failing. For user preferences, the *right* way to save them on OS X is using the CFPreferences API. Do a search on developer.apple.com. If the data is too large...

You'd probably be best either writing your own license, or covering it under a combination of licenses. In other words, you could write: "For non-commercial or shareware use, this software is covered under the BSD license. For commercial use, it's covered the license and fee described in...

Why not just install it off the Panther CD that you purchased? Wade

Since this is financially important to your university, I'd think they wouldn't have a problem purchasing an ADC Tech support incident for you. I believe they're $125 each, or if you join the Select program, you get two incidents with your membership. Open an ADC incident on this and Apple...

If your project in XCode is setup as an application, it will automatically be created as a bundle. How is your project setup? Wade

C code is not inherently multithreaded. You do so by dividing your code into multiple tasks and creating threads. For example, you might have one thread in a game that does pathfinding, while a different thread services the network communication. One caveat (well, there's lots of caveats...

BSD Headers are in /usr/include. Wade

Well, it's possible, but not easy. It requires hacking around in the window manager in places you're not supposed to be. And no, I don't know how to do it. An application really shouldn't be modifying windows that are not its own. That's why the functionality is not readily exposed. Wade

Open a terminal window and do "man 2 mkfifo" The problem is, it's a BSD routine, not a MSL routine, so you'll have to setup your project to use the BSD headers instead of the MSL headers. Use MacHeadersMach-O.h rather than MSL MacHeadersMach-O.h as your prefix file, remove MSL from the...