Re commended reading and Netbeans configuration
Sorry to be the noob coming in blind asking the broadest questions. But I would like to try my hand at developing and need some guidance.
Firstly, I haven't touched C++ code since before 2000 where I used Turbo C++ to write the simplest of cin cout programs. So whilst I haven't forgotten the concepts, the code I'm seeing is beyond me (I'm a PHP programmer). So can someone recommend some reading material? Preferable in print form.
Secondly, I'm using NetBeans 6.5 to examine the code and at the moment it's hilighting a lot of errors because I haven't included the necessary folders for "Code Assistance". Should I include 'every' folder (and possibly sub folder) in /devlibs/include? Are there other folders that might help to include?
Thirdly, do you use "btool" in place of when you would otherwise specify "make" in an IDE? I don't really understand "btool"--I assume it makes it easier to build Inkscape than running MinGW directly? I'm not sure if I should favor using the MinGW compiler when Netbeans has support for it, especially for debugging? I have created btool and build Inkscape successfully with it.
microUgly wrote:
Thirdly, do you use "btool" in place of when you would otherwise specify "make" in an IDE? I don't really understand "btool"--I assume it makes it easier to build Inkscape than running MinGW directly? I'm not sure if I should favor using the MinGW compiler when Netbeans has support for it, especially for debugging? I have created btool and build Inkscape successfully with it.
Then it's doing its job! :-) The main reason for Buildtool is to provide a portable build environment to Windows, Linux, etc. Hopefully it should "just work."
I wanted it to be something like a faint shadow of Ant, (which I love). As many of its tasks as possible are internal, especially simple ones like copy, delete, etc. It only "shells out" for things it can't provide. That way we don't worry about whether to use "copy" or "cp", "rm" or "del", etc.
Also, some of its tasks are directory-based rather than file-based. This way, files don't need to be explicitly listed anywhere. For <cc>, for example, a directory is scanned to determine dependencies. Instead of saying "compile this .cpp file to this .o file", you would say: "compile this directory of .cpp to this directory of .o"
I don't use an IDE, so I don't have a preference, but some of the devs here use Eclipse, so you might get configuration tips from them.
bob (ishmal)
microUgly wrote:
Firstly, I haven't touched C++ code since before 2000 where I used Turbo C++ to write the simplest of cin cout programs. So whilst I haven't forgotten the concepts, the code I'm seeing is beyond me (I'm a PHP programmer). So can someone recommend some reading material? Preferable in print form.
I started from a similar situation some time ago, and I still don't understand most of the codebase. It's simply much too huge to comprehend all of it. I'd recommend just starting to debug some seemingly trivial bugs and see how far you can get with that. One day you can start thinking about adding new tools and such. I haven't gotten that far yet myself, because there are still enough snapping bugs to tackle and small snapping features to add.
Secondly, I'm using NetBeans 6.5 to examine the code and at the moment it's hilighting a lot of errors because I haven't included the necessary folders for "Code Assistance". Should I include 'every' folder (and possibly sub folder) in /devlibs/include? Are there other folders that might help to include?
As Bob said, some devs are using Eclipse (including me). I don't know of anyone using NetBeans. Using any IDE makes browsing the codebase a breeze. When using btool together with Eclipse on Windows though, you will find that Eclipse doesn't parse the error code well. But that could just be my setup. Using Eclipse with gcc on Linux though works flawlessly over here.
Diederik
On Wed, Sep 10, 2008 at 2:52 PM, Diederik van Lierop <mail@...1689...>wrote:
When using btool together with Eclipse on Windows though, you will find that Eclipse doesn't parse the error code well. But that could just be my setup.
I've tried to make it work better in Windows, but without any luck. I think it's just the nature of using a non-standard tool within the IDE.
Gail
participants (4)
-
Bob Jamison -
Diederik van Lierop -
Gail Carmichael -
microUgly