|
From: | Michael Riedl |
Subject: | Re: Substituting local modules with the same name as the GM2 modules |
Date: | Fri, 17 Nov 2023 14:05:59 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 |
John,interesting topic - I have a similar issue with a module FIO I created "ages ago" but which is conflicting the the "non standard" FIO module in GM2.
For Storage I see objects m2pim_Storage_ALLOCATE & m2pim_Storage_DEALLOCATE (or m2iso_Storage_ALLOCATE & m2iso_Storage_DEALLOCATE for the ISO library). If you have a local Storage module that should have object names Storage_ALLOCATE & Storage_DEALLOCATE - so that should not give an issue at link time in my view.
But I face the situation that the compiler is hassling with the definition modules when compiling the main module - here I get complains about not implemented procedures and the like (seems it compares either my local definition file with the library implementation file or visa versa).
So I am also looking forward to the answer without the need to rename all ...
Gruß Michael Am 16.11.23 um 23:46 schrieb john o goyo:
Greetings, Gaius.I am trying to build some old code that uses a different version of Storage. I have a local version to reflect this and I am using the "-I" directive. The compiler picks up my local version for compiling local modules but it also uses my local version for gm2 modules.In particular, examining m2/m2pim/Indexing.def pulled in my local Storage.def and failed.Hence my query: Is it even possible to instruct the compiler to use local modules for local compilation only (or must I rename them)?Sincerely, john
[Prev in Thread] | Current Thread | [Next in Thread] |