newtonSDK Licensing

[hicham]

If you don't want your code modified, you can release it under a restrictive license. Example :

"This library's source can't be used in a modified form without the authors permission. To report a bug, be sure to reproduce it with the official binaries ... "

[hicham]

Can you at least compile with -fPIC ?

[Julio Jerez]

the 64 bit version is compiled with -fPIC flag

when I try the 32 bit the compiler fail, I do not know why

[hicham]

the 64 bit version is compiled with -fPIC flag

when I try the 32 bit the compiler fail, I do not know why

Any error message ?

[Stucuk]

If you don't want your code modified, you can release it under a restrictive license. Example :
"This library's source can't be used in a modified form without the authors permission. To report a bug, be sure to reproduce it with the official binaries ... "

That wouldn't mean people wouldn't illegally start there own branches. Since Julio isn't a company he most likely wouldn't waste his time or money trying to sue anyone who breached the license. In any case, if you couldn't do anything with the source code, then it would be completely pointless making it Open Source. The point of Open Source things is to share stuff with the world, not to make it so people can only look, but never do anything with it. Closed Source style Open Source doesn't give any benefits to the Project or to anyone who could download it.

You either make something Closed Source, or make it Open Source. There is no middle ground.

[Julio Jerez]

the 64 bit version is compiled with -fPIC flag

when I try the 32 bit the compiler fail, I do not know why

Any error message ?

I do not remember, I will run the make file again tonight and let you know.
why is opction -FPIC important?

Did you know that Newton comes in form of static Libraries in Linux, you cna just link to teh static library, and add any option you want.

[hicham]

why is opction -FPIC important?

-fPIC is needed to properly load shared libs into memory without overlapping with other programs/libraries address spaces : http://en.wikipedia.org/wiki/Position-independent_code ( I got a ***stack smashing detected*** btw when using libNewton.so )

Did you know that Newton comes in form of static Libraries in Linux, you cna just link to teh static library, and add any option you want.

I prefer to use shared libs to reduce memory usage and ease maintainance ( since i will just have to update the shared lib in case of a released bugfix ), but I need the objects to be compiled with -fPIC for that.

[Julio Jerez]

Ok I will try the -FPIC flag in 32 bit in linuix tonight.

[Julio Jerez]

you are right it buidl wi teh option -fpie, for soem reason I was using -fpic instead of -fpie
you can download 2.24 wit teh fix from the download page

[Carli]

The point of Open Source things is to share stuff with the world, not to make it so people can only look, but never do anything with it. Closed Source style Open Source doesn't give any benefits to the Project or to anyone who could download it.

You either make something Closed Source, or make it Open Source. There is no middle ground.

I would like to have current linux builds in each release - or the source code to build it myself for each platform I want.
And you see, Julio does NOT have the time to release the SDK for each platform in each release. So there IS a reason.

SDK on demand - we build ourselves when we need a newer version with a bugfix and Julio does not need to upload for each platform that no one will use.

[Stucuk]

Having Linux releases not take a few days longer isn't a good enough reason to open up the entire source code. The main reason things are taking longer to be fixed(And other OS's SDK's built) is because Julio is working on an Editor. So he isn't spending all his time tracking down bugs and building the SDK. Once the editor is done, things should go back to normal(Where there is little if any delay between each OS's build being released).

[Carli]

Its not just the Linux releases.

You have also some Visual Studio versions not supported, no MAC build, a few platforms like linux ARM are also missing (and it would not make sense for Julio to do these platforms at each release..)

[Stucuk]

There is a Mac build. Macs have had the same support as Linux. As long as the major platforms are covered then it should be good enough.

You have also some Visual Studio versions not supported

You don't need Lib files. Linux and Windows have DLL's(And yes i know there not called "DLL" on Linux). Im sure Linux's API has bits simmer to Windows's Dynamic DLL loading. With Delphi i can't include the lib file, yet i should still be able to port it to a Mac or Linux even tho Delphi is not officially supported.

In any case, nothing you have said is a proper reason for releasing the source code.

[hicham]

That wouldn't mean people wouldn't illegally start there own branches. Since Julio isn't a company he most likely wouldn't waste his time or money trying to sue anyone who breached the license. In any case, if you couldn't do anything with the source code, then it would be completely pointless making it Open Source. The point of Open Source things is to share stuff with the world, not to make it so people can only look, but never do anything with it. Closed Source style Open Source doesn't give any benefits to the Project or to anyone who could download it.

At least developers can compile it as they want it. And distributions can include it ( since that is how Linux works ).

You either make something Closed Source, or make it Open Source. There is no middle ground.

That is your personal opinion, and I respect it.

@ Julio Jerez : I am sorry if this thread is off topic.

[Julio Jerez]

I do not care,
I never undesrtood why in some forum people get upset if some one introduce anopteh topic on a thread.
It is s a forum for god say, as long as it do not offend anyone and does not talk abouy issues that create flame war It does not matter to me.

I restrict some topics beacause they are pick by google and yahoo scrowllers the moment they mention my name, the name of someone known,
or some trade mark, and that has already caused me personal problems.