Author Topic: New to Code::Blocks (and IDEs in general!)  (Read 1093 times)

Offline Bytebro

  • Single posting newcomer
  • *
  • Posts: 1
New to Code::Blocks (and IDEs in general!)
« on: August 08, 2019, 05:12:59 pm »
Hi,

I'm an experienced developer (40yrs+), but I'm pretty old school and have always just built a makefile that does what I want!

The scenario I'd like advice about is like this.  I have a bunch of source files which go together to build a library.  Fine, I have just set up a Code::Blocks project file that successfully build my library in both Release and Debug, which is great.  The thing is, I have a number of additional source files which each build a standalone exeutable, linked to my library, which each test specific features of the library.

What is the best, or 'accepted' structure for doing this?  I surely don't want to set up a project file for every single one of these testing tools.  Also of course, it would be sweet to be able to do the equivalent of my old makefile strategy where I would just go:

make lib
make check
make install

If anyone can point me at any resources where I learn more about structuring projects, and how to achieve what I'm trying to do, I'd be really grateful!

Thanks,
k

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6667
    • My Best Post
Re: New to Code::Blocks (and IDEs in general!)
« Reply #1 on: August 08, 2019, 05:24:25 pm »
If you do not wish to use a "Normal" CB Project.
Then I would suggest an "Custom Makefile" project, with different CB target for lib, check, and install.

If you do wish to use a "Normal" CB Project; I would still suggest a different CB target for lib, check, and install.

Tim S.


C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline gib

  • Multiple posting newcomer
  • *
  • Posts: 42
Re: New to Code::Blocks (and IDEs in general!)
« Reply #2 on: August 10, 2019, 11:54:55 pm »
It sounds as if the OP is not familiar with the process to create multiple targets within a project.  I'm not either - perhaps you could explain.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6667
    • My Best Post
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline jacksmith

  • Single posting newcomer
  • *
  • Posts: 6
Re: New to Code::Blocks (and IDEs in general!)
« Reply #4 on: October 07, 2019, 01:35:19 pm »
I'm new in codeblocks. I've installed codeblocks-17.12mingw but there's a problem when I open codeblock it shows a error bellow

Environment error

Can't find compiler executable in your configured search path's  for Microsoft Visual C++ Toolkit 2003.   
Please see the attachment.
Thanks

Note: I'm using windows 10 64 bit

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2553
Re: New to Code::Blocks (and IDEs in general!)
« Reply #5 on: October 07, 2019, 08:25:40 pm »
Try to go Settings->Compiler->Select "GNU gcc" from the drop down menu -> Then press "set as default" button.
Close the dialog with OK
Close codeblocks and restart it
Open codeblocks and try to create a new project.

If the error is still there: What installation program did you use?

Offline jacksmith

  • Single posting newcomer
  • *
  • Posts: 6
Re: New to Code::Blocks (and IDEs in general!)
« Reply #6 on: October 08, 2019, 10:37:56 pm »
Try to go Settings->Compiler->Select "GNU gcc" from the drop down menu -> Then press "set as default" button.
Close the dialog with OK
Close codeblocks and restart it
Open codeblocks and try to create a new project.

If the error is still there: What installation program did you use?

The problem is solved  :D
Thanks