Placement of .obj files

[Cool Javelin]

Win7 32bit, C::B 16

How do I get all .obj files to end up in the same folder as their respective .c files?

I have a folder I keep a few utility .c files I have created that I include in most of my projects.

If my project is in drive N, and I include a file from C:\Users\Mark\Documents\Programming\C_progs\Include, I get a corresponding path from my project folder with the same name, sans the actual colon.

So if my project is in N:\Customers\Accounting\Utilities\, the subsequent .o ends up in
N:\Customers\Accounting\Utilities\.C\Users\Mark\Documents\Programming\C_progs\Include.

Of course this is really unacceptable.

What I want is for the .o files to be in the include folder where the .c file is.
In this way, if I compile a c support file in another project, it won't have to be compiled again in this project.

Thanks for any help on this,
Mark.

[oBFusCATed]

Do you use C::B projects?

[sodev]

What you are trying to do is quite a bad idea. You dont only want to do an In-Tree build instead of an Out-of-Tree build which complicates the clean up to get a clean rebuild but also want to share the compilation results between different projects.

That does not only couple these projects but also requires that all projects are compiled with identical compiler settings and, especially if this shared code depends directly or indirectly on defines, the same set of defines. Especially that last requirement is quite risky and hard to ensure. If you fail to do so you will get obscure and extremely hard to debug errors.

If you want to share code, either turn that shared code into a library and include that into your projects as binary or include it on source level by means of your vcs like svn externals or git submodules.

[Cool Javelin]

Good idea or bad, Having to link all projects together, all those things...

All I want is the ability to make C::B put the .o file in the same folder as it's .c file.

Is that possible? And how to do it?

Thanks, Mark.

[oBFusCATed]

It depends. On the answers of the following questions:
1. Do you have a project?
2. Are you prepared to write a makefile, cmake, mason, etc..?
3. You can probably use a post build step

The internal build system always places the .o files in .obj/obj folder inside your project dir tree.
Generally the path of each object file is predictable and you can copy it to where you want it in a post build.

[Cool Javelin]

I do have a project, several in fact. Most use that common include I mentioned.

I have never written a make file, I guess I can learn how,

The idea of using a post build step is doable.

Thanks,
Mark.

[oBFusCATed]

Why don't you create a static library project for the common code?
A static library is just an archive with some .o files.