Core 300 Mac build issues

[Julio Jerez]

The biggest problem now is that the Fox GUI library does not has an xcode project, not even an OS-X framework that is ready to use as many common libaries have.
This could be a big problem. I hope they have a solution because I really like the library.
The librray has a native look, it is nto just a mater of complining the code, it takes a lot more than that.

I posted on thier forum to see if they have a solution.

[pHySiQuE]

Thanks I will try it out tomorrow

[Bird]

After compiling the coreLibrary_300 Xcode project, I made a simple console app to test Newton on my Mac and am getting crashes on any Newton calls.

Code: Select all

#include <Newton.h>

int main( int argc, const char * argv[] )
{
NewtonWorld * world = NewtonCreate();
NewtonDestroy(world);
}

When I run the program I get a "Segmentation fault: 11" error message. Can anyone else confirm this?

-Bird

[Julio Jerez]

oh, I am getting too old.
I did not think fo makin a test project liek that to make sure the library is OK.
I will do that this saturday.

It is probably crashing on the thread code. since it is the only part of the engine that is OS dependent.

[pHySiQuE]

The library project compiles just fine on Xcode 4.3.2. Congratulations and thank you.

[Bird]

The library project compiles just fine on Xcode 4.3.2. Congratulations and thank you.

Are you able to use the library in your own project? Newton just crashes here when I try.

-Bird

[pHySiQuE]

No, I have not actually tested it yet.

[Julio Jerez]

Let me see if I undestand thsi correctly.

if an application is compiled entirely using LLVM front end, does this means that any platform with an LLVM just in time compiler can run that APP?
not need to port to any language? for example the engine should run on Iphones, and all Apple mobiles. and I getting this right?

If this is they way I think, then I beleive it is awesome.

[pHySiQuE]

No idea. I barely know what LLVM even is.

[carli2]

Let me see if I undestand thsi correctly.

if an application is compiled entirely using LLVM front end, does this means that any platform with an LLVM just in time compiler can run that APP?
not need to port to any language? for example the engine should run on Iphones, and all Apple mobiles. and I getting this right?

If this is they way I think, then I beleive it is awesome.

Not really. LLVM is a platform independend bytecode language, but the generated code is platform specific. LLVM-ir is the internal representation for all frontends (multi-language), optimizers (they transform llvm-ir) and code generators (they transform it into asm)
Just think about a '#ifdef 64bit', that cannot be compiled platform independent.

[Julio Jerez]

It that is teh case, Just another solution in search of a problem from some self appointed expert.
basicaaly it is and intemediate layer to make ecerything slower than as optimizing, and more also complex.
what was I thinking.

let me guess, I bet this is also another prodigy idea for the Khronos group, a group that have never inveted something that was not there before and was faster and better until they touch it.
every 5 to 6 year there re-invenet what already exist, so attract full everyopne for 5 or 6 years until every one find that it was something that came out of someone Ass at the Khrosnos group.
Collada, OpenCL, OpenGL ARB, and now LLVM.


It will make sence if tjsi was a hrawere indedet byet code that will make app run of any hardware with a LIT compiler, what good does it make to compeil teh code to a format that
will be compiel at loading with more restrition and slower code generator? did some body run out of ideas.

[drawtree]

It's hard to me to understand your question. Anyway I wish folks here to understand about LLVM a little more, and I write my understanding about LLVM.

*LLVM* is more close to a code transformer rather than runtime. Low-level means it abstracts hardware level rather than OS level.
*LLVM IR* is just a intermediate code form to transform (or compiles) one code form to another code form. It can be treated as a little higher level of assembly language.
*LLVM Compiler* exactly means *Clang* compiler. Just another C/C++/Objective-C compiler mostly compatible with GCC in most behaviors and compile options.
*LLVM GCC* means modified version of GCC to produce LLVM IR instead of native code.

As far as I know, LLVM is primarily designed to produce statically compiled native code rather than running its own byte-code. It's core idea is using hardware-neutral assemble language to compile native code. LLVM has been used as a library rather than platform to get hardware-independence and compile-time optimization.
LLVM performs optimization while compiling IR into native code. Clang also performs optimization while it compiles C family code into IR in higher level.

Actually, Apple does not use any running VM runtime on iOS. All what they are doing on iOS is just running native code statically compiled with Clang and LLVM. Clang converts C/C++ code into LLVM-IR, and LLVM compiles LLVM-IR into native code. In theory, if you have pure LLVM-IR code, LLVM can produce native code for you on any supported platform. If your C/C++ source code is compilable with Clang, it means you can produce native code on any supported platform.

For example, there's LLVM-IR -> Javascript compiler which enables running existing C libraries on web-browser. Currently, they have working version of OpenGL-ES, SQLite, Box2D, Bullet, freetype and etc on web-browser. Check it out here. https://github.com/kripken/emscripten/wiki
Of course, if you're using some platform specific feature like SSE or NEON, it's out of range supported by LLVM.

Personally, I'm betting on LLVM/Clang, because currently, it's the only practically usable facility enables static transformation of C-family code into another code. And also I expect it will become very generic code transformer.

[Julio Jerez]

In the Mac the engien does compile right when chosing LLVM from xcode

[carli2]

LLVM is a compiler infrastructure including the whole stack you need to create compilers: parsers, a c compiler, a optimizer, a code generator, a JIT engine and a linker.
And LLVM is able to detect SSE patterns from the code. I tried it for a 4x4 matrix multiplication written down in naive code and it worked

Can you create clang based makefiles that work for Linux AND Mac? That would unify the project mess.

[Julio Jerez]

Carliu, I think we are seen some very different you and I.
you keep saying the project is a mess, it is full of Bug, uninilized variables, while bunch of pejorative adjectives, but each time I ask waht it si that you want, you reply with generalities tha do not really help.