Open for suggestion, I'm not a C++ person, but want to learn with SL Viewer - Mokelembembe Mokeev 22:03, 7 April 2007 (PDT) Src/Makefile.am: required file `./depcomp' not found I tried copying /tmp/expat/lib/* into /usr/local/lib which seems to get pass the missing libexpat error, but the comes up with error: Looks like the libexpat* in /tmp/expat/lib need to be copied somewhere but not sure where. I get same error using gcc 3.3, OS X 10.4.9 PowerPC using the beta-1.14.1.1 code:
#Kokua viewer beta Patch#
When I apply patch 3 i get: Hunk #1 succeeded at 120 (offset -1 lines). Applied patches as prescribed but after doing the final make I get: "configure: error: libexpat not found make: *** Error 1" I can't compile using GCC 3.3 Eelke Folmer GCC 4.0.0 / OSX 10.4.9 ~username/ refers to the home directory of username. For reference, the single character ~ refers to your home directory but only if it's used as the first element of a path specification - ~/Desktop refers to your Desktop folder. If you're not familiar with the use of the Terminal, then you will likely find a book on using UNIX very helpful.
#Kokua viewer beta mac os x#
Remember, Mac OS X has the technological underpinning of BSD UNIX. would refer to the root directory that contains the Users folder. refers to the parent of the parent folder - from /Users/yourusername/. David Frantisek 19:55, 8 January 2007 (PST) It seems like there are a couple places here where problems are created because of the use of "./." I'm not all that familiar with use of the terminal, but I think this puts you in your home directory, which is okay as long as that's the top-level of your project, but not if the top-level is ~/Desktop or somewhere else entirely. Switching to GCC 4.0.1 does the trick Eelke Folmer Problems with directions I found out that is because i'm using an intel mac. configure: error: C compiler cannot create executables". In the third step i'm getting a "checking for C compiler default output file name. I'm a bit confused about the Mozilla lib dependency-perhaps if someone knew what was actually required to be compiled (even if it would be somewhat difficult) we could at least try. :-) Thanks. I thought the same thing also, I left the "Installing Proprietary Libraries" before "Installing Libraries as like an intro, then I moved the "Fmod" section after the section "Installing Libraries From Scratch" and before the "Boost" section - Mokelembembe Mokeev 04:53, 7 April 2007 (PDT) I'm just looking at the material for the first time, so I won't do the move myself in case I'm missing something. I suggest the section "Installing Proprietary Libraries" should come after the sections "Installing Libraries" and "Installing Libraries From Scratch", as the instructions on fmod installation require that the main directory structure has been established. Ordering of main and proprietary material installs Onward Lee Ponzu 16:00, 23 September 2010 (UTC) Possibly using LLVM will be faster, and produce faster code. It includes a totally new compile/link architecture. 106 does not seem to work.Īs a side note, Xcode 4.0 is coming soon.
The latest version of the tools: XCode 3.2.4, CMake 2.8.4, etc., seem to work fine. Thank you for your attention! Hunting Hare 12:06, 9 April 2007 (PDT) I have not verified the build processes for all of the dependent libraries yet. Apple recommends that all projects migrate to gcc 4.0 as soon as practical, for PPC as well as Intel architectures.Īt this time, if you use the precompiled libraries package, the macview source can compile and be linked using gcc 4.0.
#Kokua viewer beta code#
There are known incompatibilities between gcc 3.3 and gcc 4.0 (some code that compiles on 3.3 won't compile under 4.0). If you are targeting an Intel-based Mac, you MUST use GCC 4.0. GCC 3.3 DOES NOT TARGET INTEL-BASED MACS. This helps us figure out if there are problems introduced from an older version to a newer version. In addition, please post the name and version number of what you're compiling. Thank you! Hunting Hare 01:36, 15 January 2007 (PST)
This will help identify the environments that have issues, and allow the creation of workarounds specific to those environments. When you report any problem, PLEASE post your OS version and version of Xcode.
0 kommentar(er)
