ChibiOS Free Embedded RTOS

I can't see any viable solution for paths outside the user project directory, that includes the case where the user project is actually inside ChibiOS/RT source tree, though not my case (it's in ../ChibiOS-RT261).

Problem is that for a static rule to match the object file and the source file paths must coincide, except for prefixes. This applies to your suggestion of unique names for object files, besides it would not be trivial to make those names not only unique but fixed for each source (otherwise the object would be recreated on each compile).

There's a possible solution but it's ugly as hell: generate a per source file makefile to be included, kind of how it's done for dependencies. That way you can arbitrarity link any object file to any source file.

There are though a couple of paliative measures I would implement for the next release:

1- Rename "shell" to "chshell" or something like that. "shell" is a filename too likely to cause conflicts. See if there are other files that would be advisable to rename.

2- Remove the sorting from SRCPATHS assignment. As far as I can see it serves no purpose, whereas removing it gives the user a chance to order his CSRC sources in order to give precedence to his own files over ChibiOS/RT files in case of conflict (all $(CHIBIOS)/whatever sources should be at the end of the CSRC assignment in the user's Makefile). Also it would be a good idea to add a comment in the template makefiles describing the potential problem and advising to place all ChibiOS/RT sources at the end of the CSRC assignment.

Symlinks?

Two approaches:

a) Have the makefile create in build/lnk/ symlinks to all the source files, then use those symlinks as the actual source prerequisites.

PROBLEM: what about filesystems that don't support symbolic links?

b) Forbid to use sources outside of your project's directory, by either warning that it may wreak havoc or having the Makefile issue an error message.

The modify the Makefile as I described in a previous message so that the source tree is replicated into the build/obj/ directory.

The user would be responsible for creating symbolic links into his project to other source folders, mostly to ChibiOS/RT sources.

PROBLEM: again, what with filesystems that don't support symbolic links?.

The most feasible suggestion is to work on file names to make them more unique: chshell.c, haladc.c etc. This could be done in 3.0. Introducing a collision check is also possible.

Putting different restrictions in order to avoid a restriction does not sound like a solution.

Giovanni

Totally agree. The most practical and quick fix is to prevent name collision by renaming certain ChibiOS/RT files.

My suggestion to "forbid" using sources outside one's project is not actually a restriction, more of an obligation to use symbolic links in order for the make system to work properly. But yes, anyway I don't like that solution either.

I'll give it a bit more though just in case, but I doubt I could come up with a good solution if you haven't already.

Thanks.

From my Win32 Makefile adjusted to solve this naming file conflict problem....

Hi,

How it is done exactly? do you recreate a subtree or what?

Giovanni

Yes it recreates a sub-tree.

For some reason it doesn't seem to have issues with ../ in the path.
From my project directory I reference the ChibiOS path as ../chibios

Ahhh. I had a look at why it had no problems with the ../

Because I am creating the object files in the .build/.obj directory, a single level of ../ moves the ChibiOS directory into the .build directory. Everything is still contained nicely out of site and there are still no naming conflicts so that works for me (even if not all that was originally intended).

So the solution provided works for a single level of ../ in the source file path.