When I build an OpenVistA SemiVivA or OpenVistA VivA release, I do the
following:
<<Assume that I am in some place like /usr/local>>
source /usr/local/gtm/gtmprofile
cd o <<Change to the directory where you want the .o files>>
find ../r -iname \*.m -print -exec mumps {} \;
This compiles everything. Repeat for all the places where you have
source code.
-- Bhaskar
On Mon, 2005-07-25 at 11:17 -0500, Kevin Toppenberg wrote:
> Perhaps this is one of those situations where non-GT.M
> code creates compile-time errors, but the code will
> run anyway.
>
> Is there a way that I can tell all the code to
> compile, so I don't have to encounter syntax errors
> whenever I wander into a new part of VistA? When I
> see errors, I think I have done something wrong....
>
> Kevin
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
