Author Topic: Portable Code::Blocks  (Read 111439 times)

Offline Biplab

  • Developer
  • Lives here!
  • *****
  • Posts: 1874
    • Biplab's Blog
Re: Portable Code::Blocks
« Reply #90 on: April 24, 2011, 04:35:58 pm »
@Biplab
The v1.0.1 CbLauncher archive at codecutter.org has been updated with the changes to copyright you suggested.
I suggest however committing the same, except without the exe.
You can download that from http://CbLauncher.codecutter.org/CbLauncher_1.0.1_src.zip (334 kb)
Thanks.

I have added it to trunk; in revision 7125.

This will not be built by default. So whoever needs it has to build it by opening Project file inside tools\CBLauncher folder.

Please feel free to post patches towards improving it. :)
Be a part of the solution, not a part of the problem.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5219
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: Portable Code::Blocks
« Reply #91 on: April 25, 2011, 02:38:51 am »
@Biplab
The v1.0.1 CbLauncher archive at codecutter.org has been updated with the changes to copyright you suggested.
I suggest however committing the same, except without the exe.
You can download that from http://CbLauncher.codecutter.org/CbLauncher_1.0.1_src.zip (334 kb)
Thanks.

I have added it to trunk; in revision 7125.

This will not be built by default. So whoever needs it has to build it by opening Project file inside tools\CBLauncher folder.

Please feel free to post patches towards improving it. :)
nice, waiting this for about one year more.... :wink:
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline codeur

  • Multiple posting newcomer
  • *
  • Posts: 113
    • Code::Blocks EDU-Portable
Re: Portable Code::Blocks
« Reply #92 on: April 25, 2011, 10:31:13 am »
Thanks Biplab. A few updates are likely, but the launcher is currently used a lot around here under several Windows versions, so I am confident patches won't be needed as frequently as if we had committed earlier.