User forums > Using Code::Blocks

C::B Newb - Trying to use C::B for NaCl Development

<< < (2/3) > >>

thomas:
You probably want to make 2 build targets, because changing the filename from 32 to 64 obviously won't do much for the binary executable. Just give the output files different names (and of course build flags and libs!) in both targets and you're good. It's the simplest thing, too.

p.s.: Did it never occur to anyone that something like NaCl is an entirely scary idea? Though of course it didn't even occur to the Google guys to research the name before stealing it from another project predating theirs by 2 years...

Kyall:

--- Quote from: thomas on April 17, 2012, 10:51:50 am ---Though of course it didn't even occur to the Google guys to research the name before stealing it from another project predating theirs by 2 years...

--- End quote ---

Is the NaCl a derivative of that project?  Or did they just get to the copyright first?

I ended up doing the 2 build target thing, since it'll be a project template it isn't too rough to have that since it's not like I'll have to config it every time.  Will be looking into this more tomorrow, thanks for all the help guys, really made things easier for me.

As for the second question that was to try and avoid the 2 build targets, but after reading some doc and looking and that I figured the only way is the 2 build targets, the only way without changing source code or what have you.  Debugging's going to be a prick though since there isn't an NaCl emulator, you just have to run it in the browser.  Hope chrome comes out with a debug emulator that can be used to run nacl projects soon, the compiler options that c::b has look extremely useful, if only nacl wasn't missing a couple of the exes.  (debug and resource thing)

Kyall:
Got a problem, every time I boot code::blocks the settings I set up for the compiler are gone, does anyone know what settings file or whatever it is that windows isn't letting write permissions on that is causing this problem is located, because I haven't found it in the install directory or my local data....

oBFusCATed:
%APP_DATA%/Codeblocks/default.conf

thomas:

--- Quote from: Kyall on April 17, 2012, 01:09:01 pm ---
--- Quote from: thomas on April 17, 2012, 10:51:50 am ---Though of course it didn't even occur to the Google guys to research the name before stealing it from another project predating theirs by 2 years...
--- End quote ---
Is the NaCl a derivative of that project?  Or did they just get to the copyright first?
--- End quote ---
No derivative. NaCL is a networking and crypto library started at the TU Eindhoven in 2008 with the first release in 2009 and to date maintained at DJB's site, wrapping curve25519, salsa20, poly1305 and such into a high-level framework.

Navigation

[0] Message Index

[#] Next page

[*] Previous page