Re: EDM's and base/configure/RULES_ARCH's use of $(TOP)

[Janet Anderson <jba@aps.anl.gov>]

You can create your own TOP directory structure for development of epics 
extensions by executing the script makeBaseExt.pl
               mkdir  <mytop>
                cd <mytop>
              <fullpathname>/base/bin/<epicshostarch>/makeBaseExt.pl -t 
example <myextensionname>

This command will create an example extension which you can use to get 
started on developing you own.

Janet

Carl Schumann wrote:
> Hi,
>
> I am writing a shared library to extend EDM to support PVs that use a 
> proprietary protocol here at FNAL in addition to standard channel 
> access PVs.   For source code management reasons I want to keep my 
> work separate from standard EPICS base and EDM proper.
>
> My first thought was to change TOP when I specify it in my Makefile 
> from "../../.." to an absolute path to our official EPICS extensions 
> directory.   (The official directories are intended to contain only 
> the standard source, etc. from ANL and ORNL.)  Unfortunately, that 
> does not work because base/configure/RULES_ARCH's target, 
> $(buildDirs), appears to assume that TOP is always a relative path and 
> appends another ".." to TOP to make up
> for being in the O.linux-x86 directory under my source directory 
> instead of being in the source directory itself.
>
> Is there some other way to maintain the source code separation that I 
> seek please?   Thank you for your time.
>
> Sincerely,
> Carl Schumann