Author Topic: Some C::B Suggestions...  (Read 25064 times)

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Some C::B Suggestions...
« Reply #15 on: November 17, 2006, 05:46:14 pm »
if you dl cint5.16 there is no stdio.h file included,

but if you have installed cint5.15 before,

ftp://root.cern.ch/root/cint5.15.tar.gz

there is one and then it will work

 8)

takeshimiya

  • Guest
Re: Some C::B Suggestions...
« Reply #16 on: November 17, 2006, 07:37:53 pm »
And I wouldn't recommend doing that, the cint 5.15 is more than one year old. The 5.16 does come with stdio.h

It's just easier to do what the main page says:
* Source package for all platforms (1.3MB) (with auto-compile scripts for most of the platforms)
* Binary package for Windows-NT/95/98/2000 (1.2MB) (download the source package too)

Uncompress the binary and the sources in the same folder and that's it.

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Some C::B Suggestions...
« Reply #17 on: November 17, 2006, 07:57:37 pm »
The 5.16 does come with stdio.h

it didn't when i tried it, otherwise i wouldn't post it

takeshimiya

  • Guest
Re: Some C::B Suggestions...
« Reply #18 on: November 17, 2006, 08:12:30 pm »
The 5.16 does come with stdio.h

it didn't when i tried it, otherwise i wouldn't post it
now that I look the original tar, that's true: the std* headers are "generated" when you compile, because in the new version they are generated when you make the rule include/iosenum.h, to match the compiler and platform configuration used (so it will work with compilers other than VC, like MinGW).

so then, if you want only the interpreter and don't care mixing interpreted code with compiled code, or don't care for compiling cint, do what tiwag suggests above. :)
otherwise, (you want to use makecint, want to compile cint, or want the latest ver.), do what I said above. :)

Shakes

  • Guest
Re: Some C::B Suggestions...
« Reply #19 on: November 18, 2006, 01:52:30 am »
OMG that CINT thing is awesome. Its like running the iPython shell or equiv.

Can u say "Kicks Python around like never before!" *Smack*, *Smack*, *BASH*

Someone make a plugin quick! "GO, GO, GO!"  :P
« Last Edit: November 18, 2006, 01:55:06 am by Shakes »

takeshimiya

  • Guest
Re: Some C::B Suggestions...
« Reply #20 on: November 18, 2006, 04:05:19 am »
OMG that CINT thing is awesome. Its like running the iPython shell or equiv.
Or it is even better :), as you can mix C/C++ interpreted and C/C++ native code.
"You can encapsulate arbitrary C/C++ code as a precompiled library. Precompiled library can be configured as a DLL and access between interpreted code and precompiled code can be done seamlessly in both directions."

Can u say "Kicks Python around like never before!" *Smack*, *Smack*, *BASH*
And it's also cool that the ROOT/CINT framework will be used in Large Hadron Collider(LHC) research project beyond 2020. :P

Someone make a plugin quick! "GO, GO, GO!"  :P
Until a plugin gets made, or the compiler framework gets redesigned, you can use makefiles build system in C::B, or for simple programs, create a Tool. :)

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Some C::B Suggestions...
« Reply #21 on: November 18, 2006, 08:41:16 am »
...otherwise, (you want to use makecint, want to compile cint, or want the latest ver.), do what I said above. :)

can you explain exactly how you've built cint using the cint5.16.tar.gz ???

i tried using msys and mingw
./configure --arch=mingw
make


then there is an error when it wants to build readline, which isn't in the package,
how did you solve this ?

takeshimiya

  • Guest
Re: Some C::B Suggestions...
« Reply #22 on: November 18, 2006, 08:53:46 am »
can you explain exactly how you've built cint using the cint5.16.tar.gz ???

i tried using msys and mingw
./configure --arch=mingw
make


then there is an error when it wants to build readline, which isn't in the package,
how did you solve this ?

As I said above of above :P :

For compiling it, just open msys and do a ./configure --arch=mingw && make it works for me.
You might need to remove (or compile) readline and dl from linking libs if you don't have them.

I'm not quite sure what dl does, but readline is not really needed, so I removed it from the linking libs.
I guess that if you want it, you can compile it or use this precompiled library.

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: Some C::B Suggestions...
« Reply #23 on: November 18, 2006, 08:57:15 am »
As I said above of above :P :

For compiling it, just open msys and do a ./configure --arch=mingw && make it works for me.
You might need to remove (or compile) readline and dl from linking libs if you don't have them.

I'm not quite sure what dl does, but readline is not really needed, so I removed it from the linking libs.
I guess that if you want it, you can compile it or use this precompiled library.


yes i've read that, please exlain a step by step procedure what is necessary to
remove it from the linking libs ??? which file to edit ?? what to edit ??
that would be a helpful information.

takeshimiya

  • Guest
Re: Some C::B Suggestions...
« Reply #24 on: November 18, 2006, 09:07:48 am »
yes i've read that, please exlain a step by step procedure what is necessary to
remove it from the linking libs ??? which file to edit ?? what to edit ??
that would be a helpful information.

Open the configure file in a text editor, and search for the function config_mingw (@line 155).
There, add this empty variable in one line: BUILDREADLINE= and this on another: DEFAULTLIBS=
With that, you'll be overriding the values specified in function config_GCC_defaults.

I'm not quite comfortable with the (new) building system it haves, so it might be better if we write a CodeBlocks project or premake script.

Offline dmoore

  • Developer
  • Lives here!
  • *****
  • Posts: 1576
Re: Some C::B Suggestions...
« Reply #25 on: November 18, 2006, 09:28:08 am »
OMG that CINT thing is awesome. Its like running the iPython shell or equiv.

Can u say "Kicks Python around like never before!" *Smack*, *Smack*, *BASH*

I guess I should stop working on my C::B python plugin (debugger and project manager) and go cry in a corner or something  :cry:

takeshimiya

  • Guest
Re: Some C::B Suggestions...
« Reply #26 on: November 18, 2006, 09:36:36 am »
OMG that CINT thing is awesome. Its like running the iPython shell or equiv.

Can u say "Kicks Python around like never before!" *Smack*, *Smack*, *BASH*

I guess I should stop working on my C::B python plugin (debugger and project manager) and go cry in a corner or something  :cry:
No need to make a c++ vs. python, each one is with it's own users target; what was the reaction is that it is news for much people that there exists "c++ interpreters".
CodeBlocks is about multiple-platforms compilers and languages, so (please) continue doing a python plugin. If it is finished a cint plugin can be made, and so on, being based on the first.  :)
« Last Edit: November 18, 2006, 09:38:56 am by takeshi miya »

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: Some C::B Suggestions...
« Reply #27 on: November 18, 2006, 12:29:33 pm »
I guess I should stop working on my C::B python plugin [...]
Mmmmh... VS2005 was released...
...so we better should stop working on C::B and go cry in a corner or something  :cry:
:lol:
No, but honestly: A college of mine bugs me every week when Python support might be added. So far I provided him the "InterpretedLang" plugin and the python lexer. Anyway: The plugin is buggy and altogether this is not of *much* help. So I'd *love* to see a "native" python plugin myself, too.
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline David Perfors

  • Developer
  • Lives here!
  • *****
  • Posts: 560
Re: Some C::B Suggestions...
« Reply #28 on: November 18, 2006, 04:09:36 pm »
I like to see that plugin too, but that's because I want to learn Python ;)
OS: winXP
Compiler: mingw
IDE: Code::Blocks SVN WX: 2.8.4 Wish list: faster code completion, easier debugging, refactoring

Offline Game_Ender

  • Lives here!
  • ****
  • Posts: 551
Re: Some C::B Suggestions...
« Reply #29 on: November 18, 2006, 04:15:25 pm »
I like to see that plugin too, but that's because I want to learn Python ;)

Don't wait, download wxPython and try out Pycrust (a wxPython based python shell with CodeCompletion).