[gschaider]

From your question I assume that you managed to compile OpenFOAM on your Mac and have moved on to more advanced topics. I'd (politely) suggest that you ask the question (Addition of a new combustion model) on another, more appropriate location on the message board because

a) it is not Mac-specific
b) if a fruitful discussion emerges from this question it might be easier for those having a similar question to find it (a Solaris-user interested in combustion-modelling is not very likely to look at a thread titled "Build OpenFOAM on MacOSX")

[ganesan]

I am sorry to say i haven't succeeded.. to compile. But easier solution is copying again the disk image and i kept the same path :

/Volumes/MacExternal/local/OpenFOAM/ and so on..

Prebuilt applications Everything works fine. (I am still asking myself why i could not have it installed on my $HOME bcos i have changed my HDD to UFS specifically for this)...anyway this remains me a surprise...I guess either some modifs of Hervoje on scripts are not exist in the disk image or may be i am missing something!!!

Thanks a lot for helping me. As you said i will better ask in the appropriate one..

[hjasak]

As I said, this was an EXPERIMENTAL build and I'm happy to hear you can run the pre-compiled stuff. Unfortunately, compiling OpenFOAM on a Mac is still not straightforward because I had to hack through the make system (new library extension) and the lam build does not work with the standard options. I haven't got an easy way for you to do a proper build, but this will come with a future release.

Incidentally, there is a pre-compiled version of mico for OS X so we can get over that obstacle as well. As for installing in the home directory, this works for me without any glitches. /Volumes/MacExternal/ is an external disk I use for builds but with the DYLD_LIBRARY_PATH setenv I told you about before I can run off compressed disk images without the external disk (this should really work for you, I suspect you're running a different shell or not sourcing everything correctly).

Now that I know all is well with OpenFOAM on a Mac, I will probably buy a big Mac (hmm, Big Mac, I'm sure some of you get the joke) as my home machine in the next year or so and this will close the porting issues once and for all.

Hrv

[ganesan]

Thanks Hrv i will try to find the problem of my installation...

[ganesan]

/usr/bin/libtool: file: -lmeshTools is not an object file (not allowed in a library)

what is this error related to Apple libtool? Which development tool i do not have? Any help

[gschaider]

About the development Tools: I don't know which stuff comes with a blank "consumer"-Mac because the first thing I do with a new Mac is to install XCode (which usually comes with the OS-DVDs, as a rule of thumb operating systems for "real men" are shipped with a compiler, big cheers to Windows, but I digress). So I really can't tell whether something might be missing from your setup. I assume you have XCode and X11 installed. From what I remember the XCode setup doesn't automatically install the options "X11 Development" and something like "BSD compatibility stuff" (I don't know whether they're necessary for OF).

My guess with your problem is, that he finds a file libmeshTools.dylib (or .a) that isn't really a library (sometimes happens when linking goes bad). Find that file. The command 'file libmeshTools.dylib' should tell you what kind of file it is. If it is not some kind of 'dynamically linked shared library' remove it and rebuild.

[ganesan]

Again error continues and it becomes a never ending story...
well i hope this would be a final try
SOURCE=OSspecific/Unix/fileStat.C ; while compiling this file i get an error sys/sysmacros.h is not found....

[gschaider]

You re-installed the vanilla (official) OpenFOAM-Version 1.2 sources? right?

Then you'll have to encapsulate the line

#include <sys/sysmacros>

with

#ifndef darwin
#include <sys/sysmacros>
#endif

(Propably you'll have to do the BIG/LITTLE-Endian stuff discussed elsewhere in this thread and other stuff I can't remember or don't know)

[bobby_xiao]

Apparently, mico has been updated to work with Mac OS X. I was able to make mico compile, despite the fact that idlcompile was segfaulting (only at exit; the code was fine).

However, it seems that some minor change in mico have caused FoamXHostBrowser to hang when compiled with the new library. I have localized the hang to PortableServer::RefCountServantBase::_add_ref () in mico/orb/poa_base.cc (line 193): MICOMT::AutoLock l(_ref_lock);

Call Stack (traced; line numbers may not be accurate)
FoamXHostBrowser.C:77 (new IHostBrowserImpl(orb, args);)
IHostBrowserImpl.C:92 (FoamXServer::HostBrowser::IHostBrowser_var ref = _this();)
FoamX.C:25248 (CORBA:: Object_var obj = PortableServer::ServantBase::_this();)
poa_base.cc:118 (return poa->activate_for_this (this);)
poa_impl.cc:2803 (PortableServer:: ObjectId * id = __activate_object (servant);)
poa_impl.cc:2537 (POAObjectReference * por = new POAObjectReference (this, *id, iface,servant);)
poa_impl.cc:558 (servant->_add_ref();)
poa_base.cc:193 (MICOMT::AutoLock l(_ref_lock);)

The AutoLock hangs the HostBrowser process.

The lock command sits and hangs forever, and the HostBrowser doesn't work.

Are there any major differences between 2.3.11 (not-mac-compatible) and 2.3.12 (mac-compatible)?

[hjasak]

Well, if it helps you at all, I have switched to mico-2.3.12 on my linux machine and there's no trouble.

Hrv

[mattijs]

We switched over to 2.3.12 as well.

[hjasak]

Hello everybody,

I am re-porting the latest development version of OpenFOAM onto Mac OSX. Does anyone know how to make processor independent binaries? I think Apple call it Universal Binary but I'm not sure what is required.

Any guidance + a person willing to test it would be much appreciated.

Speak to me,

Hrv

[martin]

I can´t help you with guidance but am willing to test on my PowerBook G4 anytime and my MacPro as soon as I come back to office (April 12th).

Martin

Hi Hrv,

I am new in Mac and Unix world, so I cannot offer you my guidance, but I am willing to test them in my Intel MacBook. I may be slow in response though if you don't mind as I have uni, research and part-time job I have to do.

regards,
felicia

[hjasak]

Well, I've got good news and bad news. I have repeated the OpenOFAM port from y latest sources and an updated image of the library has been uploaded to the usual place:

http://homepage.mac.com/h.jasak/

As an addition to the stuff we had before, this time I got FoamX and patchTool to work using Java-Corba. The infuriating thing is that I cannot right-click in FoamX to pop up the contextual menus. It's driving me nuts and I haven't got a single mouse in the house :-) Please feel free to try out the new build and let me know if there are problems.

The bad news is related to the Intel build. In principle, this should be easy - just adding a couple of arch instructions on the appropriate link line. However, 99.9% of porting pain is in paraview, mico and lam and I really cannot be bothered with this. It would be so much easier to just build it on an Intel Mac natively. Interestingly, even paraview release does not do Universal binaries, which tells me there may be problems. With this in mind, I am sorry to say the Intel Mac build is delayed until one makes its way into my life.

For enthusiastic souls out there, I have left the packed Mac build source next to the dmg files, so you can try building on your machines. Not easy, though.

Enjoy,

Hrv

[gabriel_stokes]

Hey!

I am restarting this old thread, as all threads on this topic traces to a dead end, I've been searching through the web and this WIKI a lot now. Would be nice if one of these mac-threads actually ended up in something useful...

I have tried to compile OpenFOAM 1.4.1 using the (very incomplete) guide at http://openfoamwiki.net/index.php/Ho...e_OpenFOAM_Mac

on three different Intel mac's now, without any luck. Would anyone be so kind to write a working step-by-step guide on how to compile (that is, not using any precompiled binary) OpenFOAM 1.4.1 on an intel Mac.

Thanks a bunch.

/Mads

[egp]

Mads,

I would recommend that you use the 1.4.1-dev version. All of the OSX patches have been applied, and the rules are up to date. The OpenFOAM libs & apps should compile.

Another option is to download a 1.4.1-dev disk image from someone who has it working. I've posted a 2GB disk image from my laptop (MacBook Pro) at:

http://idisk.mac.com/egpaterson-Public

You need to

1. Create a directory named $HOME/OpenFOAM
2. Mount the disk image
3. Link $HOME/OpenFOAM/OpenFOAM-1.4.1-dev to /Volumes/OpenFOAM-1.4.1-dev
4. Add . $HOME/OpenFOAM/OpenFOAM-1.4.1-dev/\.OpenFOAM-1.4.1-dev/bashrc to your $HOME/.profile
5. Source $HOME/.profile
6. have fun!

As an aside, if anyone is running OpenFOAM on a laptop, I would recommend pulling the battery if you have it connected to the power adapter. When running OpenFOAM jobs for any length of time, as opposed to the typical laptop duties, the CPU temperature will approach 180F (87C). High temps have a big impact on battery life. I've definitely noticed a negative impact on how long my battery will hold a charge since I began running some small jobs on my laptop!

[paka]

Thanks a lot for publishing .dmg file, however it is not downloadable If this could be fixed I'll be glad to download it ;)

[gabriel_stokes]

Hey Eric,

great! This should put me on the right track. However, as Krystian points out, the .dmg is not downloadable, but I am sure this is easily fixed.

This binary-dmg way is great, but I would prefer to compile it myself using the steps you kindly described above. But, and forgive my ignorance, I do not know where to find the developer version of OpenFOAM. I assume you do not mean the ordinary source-tree from OF's homepage, because this is what I have already tried. I guess you are referring to a OF-dev.tar.gz somewhere, right?

best regards
Mads

[gabriel_stokes]

Hm...this is kind of sad...

I'd really like to use OpenFOAM on my mac, but it simply won't work. I end up spending more time on compiling than doing what I find much more fun: CFD.

Hopefully someone will help me out someday :-/

/Mads