Fix building

[ReneHollander]

This fork currently only works on linux. All platform specific functionallity like fbdev, egl, etc. should be configureable during install time.

[ReneHollander]

@piranna
Is there a way to move the building of the actual addon (target_name: ´canvas`) into another file? Then I would not have to configure which backend should get built twice.
Also now that you have some experience with node-gyp you can maybe help me out a little?

[piranna]

Is there a way to move the building of the actual addon (target_name: ´canvas`) into another file?

I'm not sure, since it's what node-gyp is compiling...

Then I would not have to configure which backend should get built twice.

Are you talking about the static and dynamic versions? Sure, you can define variables and I think they will be inherited :-)

Also now that you have some experience with node-gyp you can maybe help me out a little?

Of course, I'll review it later if you send it to me ;-)

[ReneHollander]

I'm not sure, since it's what node-gyp is compiling...

I meant that the addon gets built into a static library (canvas.lib) with a seperate build file (canvas.gyp), which will then either get linked dynamically to the dependencies, or static.
I am also wondering how I should link xlib. I don't think I can do a 100% static build with xlib but have to link it dynamically as well.

Of course, I'll review it later if you send it to me ;-)

Thanks for you help!

[piranna]

I meant that the addon gets built into a static library (canvas.lib) with a seperate build file (canvas.gyp), which will then either get linked dynamically to the dependencies, or static.

Oh, no, .node files are dynamic libraries (.so) with a different extension, and it's generated by static.gyp, that's called by binding.gyp. There's no canvas.gyp file. It could be done, but would require to rewrite both static.gyp and dynamic.gyp files.

I am also wondering how I should link xlib. I don't think I can do a 100% static build with xlib but have to link it dynamically as well.

I would test it first as dynamic one, and later try to compile as static one, since it would require to download the library sources and compile them to make the module autocontained. Also, I don't think it would make too much sense to make a static module if you are using X11 as backend, since it has already a lot of dynamic dependencies...

[ReneHollander]

Oh, no, .node files are dynamic libraries (.so) with a different extension, and it's generated by static.gyp, that's called by binding.gyp. There's no canvas.gyp file. It could be done, but would require to rewrite both static.gyp and dynamic.gyp files.

I actually meant to write a new canvas.gyp the handles the building of the sources. The resulting lib would then get linked to cairo, pango, etc either statically or dynamically depending on the config.

I would test it first as dynamic one, and later try to compile as static one, since it would require to download the library sources and compile them to make the module autocontained. Also, I don't think it would make too much sense to make a static module if you are using X11 as backend, since it has already a lot of dynamic dependencies...

I was thinking that that would be the case...

[piranna]

I actually meant to write a new canvas.gyp the handles the building of the sources. The resulting lib would then get linked to cairo, pango, etc either statically or dynamically depending on the config.

Well, as I told you, it would require to rewrite static.gyp and dynamic.gyp :-) Work on one of them and I'll merge them later :-)

I was thinking that that would be the case...

Then, no static version for X11 :-D

[ReneHollander]

Well, as I told you, it would require to rewrite static.gyp and dynamic.gyp :-) Work on one of them and I'll merge them later :-)

Thanks :D

Then, no static version for X11 :-D

We could still do a static build with cairo, but just link xlib dynamically. If you want to use the X11 backend you need X11 installed an running for it to even open a window in the first place...

[piranna]

Thanks :D

;-)

We could still do a static build with cairo, but just link xlib dynamically. If you want to use the X11 backend you need X11 installed an running for it to even open a window in the first place...

Yes, that's an alternative... One step at a time, first get it working dynamically :-)

[piranna]

I've taken a look about compile independtly canvas.a and seems it would be more difficult that I though, since they are required the headers of the libraries... :-/ Seems feasable, but not as easy as I though first.

[piranna]

Now you have in my fork an independent canvas.gypi with the configuration of canvas, and also I've added a simple selector to define what hardware backends will be compiled ;-)

[ReneHollander]

Can you maybe submit a pull request? I will take a look and want to merge it :)