Of corse you are correct. Firstly specific thanks to Jürgen for his extra explanation. Sorry for the interruption and thanks for all your kindness in replying.
Sadly it seems that I had the answer in my brain but these days it takes longer to access it. I had sent the email but then a few minutes later I realized it was a system header. respect Peter > On Sep 28, 2022, at 5:44 AM, Dr. Jürgen Sauermann > <m...@xn--jrgen-sauermann-zvb.de> wrote: > > Hi Peter, > > the problem seems to be this: > > The GNU APL build system is based on autoconf/automake which is the > standard for GNU projects and many others. > > In this build system the src directory contains all possible source files. > The build system also supports a number of different build targets; the > most common being the GNU APL interpreter binaries, other less frequently > used ones are libapl, the GNU APL python language interface, the GNU APL > erlang language interface, and so on. > > The ./configure script allows the user to choose that target that should be > built and does this by selecting only a subset of all source files in the src > directory. In particular if you build the interpreter then the file > src/python_apl.cc is NOT one of the source files selected and the > missing Python.h is not needed (and a lack of it causes no harm). > > Now, the Apple build system seems to work differently by trying to pick > all source files in the src directory as opoosed to only those needed for > the desired target. This is wrong, but ./configure cannot do anything > about it. > > The easy fix for this is to simply remove the .cc files that complain before > initializing the Apple build system. Note that there are also files that are > not > needed about which the build will not complain. The do not harm but make > the build target bigger than needed (keyword: dead code). > > Of course every 'svn up' will restore the files so it may make sense to write > a small script that removes the files. > > Best Regards, > Jürgen > > > > On 9/28/22 1:13 AM, Peter Teeson wrote: >> In Terminal: >> cd GNUapl >> svn co http://svn.savannah.gnu.org/svn/apl/trunk >> <http://svn.savannah.gnu.org/svn/apl/trunk> > svn-log 2>&1 >> >> Then was trying to see about building it as an Xcode command line project. >> Added trunk folder to project, including sub-folders. >> >> Did Build and got this message from the preprocessing. >> >> Lexical or Preprocessor Issue >> ….GNUapl/trunk/src/python_apl.cc <http://python_apl.cc/>:3:10: 'Python.h' >> file not found >> >> Did a multi-file search of trunk and sub-folders and did not find it. >> >> Please check if the .h file is missing from svn checkout >> http://svn.savannah.gnu.org/svn/apl/trunk >> <http://svn.savannah.gnu.org/svn/apl/trunk> >> >> Thanks >> >> Peter >> >> >
