repository structure? about real-time-cpp HOT 15 CLOSED

Hi I like the your book but I'm having serious problems implementing your examples.

I am seeing the previous discussions and I realize that the repository is directed to use an IDE and the process becomes seriously terrible, if that IDE is not used in particular. I think that anyone should implement your examples from a simple terminal

from real-time-cpp.

Hi Liviu,

Thank you for your suggestions. You are right. The directory structure is somewhat non-intuitive. I would like to de-couple it from the chapters of the book.

I think removing the tool chains would be a good idea. I discussed this with a few others today, and most folks agree that the tools are just a waste of space at github.

I have been experimenting with supporting the project build in Code::Blocks. It seems to work pretty well. What do you think of the portability of Code::Blocks?

Another reader found a few errors. And I found a few. So I also need to add an (easy to find?) errata sheet somewhere at github.

I am really busy with work and the release of Boost 1.56 coming up. I might commit just a few math things to real-time-cpp. But other than that, it might take me a while to re-organize the repo.

Thanks again and cheers, Chris.

from real-time-cpp.

What do you think of the portability of Code::Blocks?

I don't know, I had no prior experience with it, but I can evaluate it. Personally I had decided to take the Eclipse path, and contributed GNU ARM Eclipse.

it might take me a while to re-organize the repo

ok, when you're done, if you want another point of view, just notify me.

regards,

Liviu

from real-time-cpp.

I read again your message, and I think I skipped a detail. You said: "I have been experimenting with supporting the project build in Code::Blocks. It seems to work pretty well. What do you think..."

If that was a question about what IDE to use for your projects related to the book, my suggestion is definitely Eclipse; it is portable, support for C++ is mature, the indexer is a joy to use, not to mention the additions for ARM that I contributed with the GNU ARM Eclipse Plug-ins project.

from real-time-cpp.

Yes, I was asking what you thought the right IDE is.

That looks like impressive work with GNU ARM Eclipse. I will take a look at it. But it will take a while for me to get into it.

Thank you for your helpful suggestions.

Cheers, Chris

from real-time-cpp.

ok, no problem, take your time.

if you have any questions, don't hesitate to ask.

Liviu
[email protected]

from real-time-cpp.

@ilg-ul love the GNU ARM plugin. I use it with the Sourcery Lite tool chain.

Not understanding what this toolchain is for exactly, is it a duplication of effort? Or will you be providing it to a wider audience, I'd like to see more of a public toolchain than the Soucery version.

When I discovered this repository I was attempting to configure a toolchain for Eclipse. Finding the visual studio (VS) was great as I use VS all day. However I'd like to see it as a project template. It was beyond me, or the time I'm willing to devote, to figuring out how to use this tool chain for new projects in VS.

from real-time-cpp.

@ilg-ul OK. I have at least removed the GNU tool chains in order to reduce the size of the repo.

@jhalbrecht When working with VS, I use a project of type "External Makefile" and invoke GNUmake via the NMAKE command line options, usually using an intermediate batch file for this. This is a very difficult way to go. And you are right, VS does not supply any dedicated templates for binding an external compiler into the studio. I put a lot of effort into this methodology, but have not been able to find a way to effectively publish or distribute the technology. Maybe I need to settle down one day and really write a template for VS and, say, a GCC cross compiler...

If you look at my file build.bat, you can see how I use GNUmake to build projects.

I will continue to clean up my repo as time permits.

I am working on adding a port to the Renesas RL78 at this time. It should be available in a few weeks.

Cheers, Chris

from real-time-cpp.

There is a new version of GNU ARM Eclipse plug-ins available, with several improvements and new project templates.

from real-time-cpp.

Hi Liviu,

I would like to split this issue into two separate issues.

1. repository structure (the original issue)
2. Request to create a portable ARM(R) build with Eclipse / GNU ARM plug-ins

I believe that the removal of the binaries solves the original issue. I have created the a new issue to handle 2) above.

Can we close the original issue?

Cheers, Chris.

from real-time-cpp.

If you are happy with the result, sure.

Perhaps you could also update the readme.txt, to explain how to install the toolchain.

Regards,

Liviu

from real-time-cpp.

Hi. Thanks for the comment. Yes, I am aware of this weakness. Would *nix Makefiles for GNUmake be a good starting point? I could generate these if desired.
Regards, Chris.

from real-time-cpp.

From my experience with GNU ARM Eclipse, properly written makefiles are quite portable.

However, for Windows, the key is having a new and correctly configured & packed make, otherwise there are countless problems, like line length, paths with spaces, etc.

For those interested, I maintain a Windows Build Tools package that can be used without problems outside GNU ARM Eclipse: http://gnuarmeclipse.github.io/windows-build-tools/.

from real-time-cpp.

A generic Makefile would be a very good idea

from real-time-cpp.

The various points in this issue have been handled.
Repository structure is now cleaner.
Generic build is supported with various build improvements over the years.

from real-time-cpp.