Chronological Thread 

< Chronological >      < Thread >

---

* Andrew Miller <ak.miller at auckland.ac.nz> [2011-05-29 20:39] writes:
> On 27/05/11 09:56, Lucian Smith wrote:
>
> >
> >Would it be too much to ask for the mac binaries to be universal binaries
> >instead of i386-only? I personally would like the ppc added; others may
> >appreciate x86_64. (Particularly if you don't want to not have people
> >have to compile the API themselves on a mac.)
>
> The plan is not to make changes like that for this release; however, the
> Auckland Bioengineering Institute is working on setting up build servers
> (including a Mac running a 64 bit operating system) that could be used
> to produce universal binaries. The suggestion we have had so far is that
> supporting x86 or PPC is pointless and we should only be targeting
> x86-64 - so if you have a different use case to balance that, it could
> help us respond to that other view point when working out requirements.
>
> The downside of universal binaries is that everyone needs to have object
> code for all platforms, which is likely to increase the size of the
> binaries for everyone on Mac - alternatively, we could make two or three
> different builds.

I definitely need an i386 and not an x86-64 version--due to trying to make
everything work with the same libraries for native and java applications
for JSim, a 64-bit version would be incompatible with everything else.
Right now, JSim still supports ppc, partly because the PI on the project
still uses ppc, so he would be sad if there was no ppc version.

> >Also, I don't know how these things are usually done on the mac, but the
> >provided binaries all assume they are being installed in /usr/local/lib/
> >(you can see this with 'otool -L libcevas.dylib', as an example). The
> >installation instructions should probably mention this.
>
> You don't have to install them there, however - they work for me
> straight out of the SDK directory.

I know there can be oddnesses with applications you double-click vs.
command-line applications, but I am not any sort of Mac expert at all, so
that's basically the extent of my knowledge on the subject.

> >Finally, it would be nice if the final actual install files had different
> >names from each other, and if the Windows file was a .zip
>
> That is something we could also look into, but given how close we are to
> releasing, not something worth holding up the build for. I'd suggest
> opening a tracker item at https://tracker.physiomeproject.org/ (probably
> best you do it, so you are CCd and can put the use cases for why you
> want that, but if no one does it by Wednesday, I'll try to remember to
> do it).

I don't think this is so much something you'd need to investigate as it is
something you'd just take ten minutes to do. But I can fill out a tracker
item for it.

> >Barring the above issues, I now believe I have gotten the rc to work out
> >of the box on a mac, and with that one file copied in by hand on linux.
> >My initial attempt at getting it to fully integrate on Windows was not
> >successful, but I still have avenues to explore before I admit defeat
> >there. So close...
>
> Randall has independently confirmed it works with Java there, and I have
> a simple C++ program going on Windows too - any luck since you sent the
> e-mail? What exactly is going wrong? Also, what compiler version are you
> using (if it is MingW and not MSVC, note that these binaries are only
> going to work with MSVC; we are working on MingW binaries, but they
> won't be part of this release)?

I had had my project working in MSVC10 with CMake, and was trying to get
it to work with CellML with MSVC9. Part of the problem was that CellML
uses '#define WIN32' while libsbml uses '#define WIN32 1' or some such,
and then uses 'if(WIN32)' instead of 'if(defined WIN32)' so I had to work
a bit to sync up those different uses. Then there were some other
constants you all #defined (like 'IN' or something) that I was using in my
parser--I don't know why I only had a problem on Windows and not the other
two platforms, but there you go.

After those were fixed, something else still wasn't working, but I haven't
had a chance to figure out if the problem is my project+MSVC9 (vs. 10) or
if the problem is my project+CellML--I'll be able to give it another
go-round on Wednesday.

-Lucian

---

• [cellml-dev] CellML API Release Candidate 4 out, Andrew Miller, 05/24/2011
  • [cellml-dev] [cellml-discussion] CellML API Release Candidate 4 out, Lucian Smith, 05/27/2011
    • [cellml-dev] [cellml-discussion] CellML API Release Candidate 4 out, Andrew Miller, 05/30/2011
      • [cellml-dev] [cellml-discussion] CellML API Release Candidate 4 out, Lucian Smith, 05/30/2011
      • [cellml-dev] [cellml-discussion] CellML API Release Candidate 4 out, Lucian Smith, 05/30/2011

---

Archive powered by MHonArc 2.6.18.