Thread: Compiler/Linker work around

Hi,
I have 25 c modules.Out of these modules i generate prg file intended for two different devices.In the system these two devices work together.There is one module(Let's say module 10) with special function (let's say func_1()) in it which will be used by both device codes.Now when I compile these modules for first device it works fine as compiler knows function func_1().For second device Ican't compile module 10 as it's a requirement.Then I compile remaining 24 modules but I get error as it doesn't know func_1() which has been called from one of compiled modules.Well,this special function can not be moved somewhere else so my question is how do we work around with this situation????

Thank you very much Mr.salem.Let me illustrate whole situation.My application is Locomotive Engine control.I have two controller devices to conduct all the functionalities.One device acts as a master and other as a slave.Prototype of func_1() is accessible to both device code.There is one third party master module (lets's say master_drv.c) which defines func_1() and third party slave module(let's say slave_drv.c) which doesn't have func_1().Unfortunately func_1 is called by other global module e.g oil_system.c.When I compile code for master controller i do compile master_drv.c along with all other modules (including oil_system.c) and so all is well.But when I compile my code for slave i won't have defination for func_1() as i compille slave_drv.c(requirement) not master_drv.c which has actual defination for func_1().Also,I can't move func_1() into global module as it takes lots of dynamic variables which have been declared by master_drv.c only.I tried conditional compilation as you said but then linker will throw error for unresolved externals.I use microtech mcc68k compiler.Any ideas???.

Ewe, yuck. Perhaps you should define a structure with function pointers in your new code that reference the old code (or vice versa) so that you can "register" your new functions in the old code and perhaps even break out the old functions in the new code. -- This is often done in the Linux kernel so that code can be reused without junking up the name space too badly.