Steve Fryatt
2020-05-11 15:04:10 UTC
I've been attempting to build a version of the current DeskLib for use in
the GCCSDK, based on the sources at https://www.riscos.info/websvn/
A minor syntactical tweak to Makefile.unix notwithstanding, it seems to do
the right kinds of things, and
make -f Makefile.unix SCL=true install
puts the expected files into ~/gccsdk/env/...
If I then try to use it to compile an application (in this case WinEd from
the same source as above), then again it seems to do the correct sorts of
thing (except that WinEd's Makefile requires a lot of modification to make
it happy with the GCCSDK), but the process soon hits several problems.
The first, which I would like to sort out before moving on to the rest, is
that the DeskLib headers installed by the process above contain several
#include "DeskLib:Core.h"
lines and similar, which GCCSDK can't sensibly resolve. I can make things
build to a point where I'm looking at a handful of genuine-looking missing
or conflicting source files in WinEd by doing a search and replace to remove
the <DeskLib$Path> references from within ~/gccsdk/env/include/DeskLib/, but
this seems sub-optimal. Not least because the DeskLib docs refer to the
library being prepped for use in the GCCSDK, which suggests that this should
"just work". :-)
Is there some way to make GCCSDK happy with the files as they stand,
"DeskLib:Core.h" and the like included?
Also, where's the best place to ask about DeskLib nowadays. The last SVN
commit was 2012, and the Google Group that the documentation recommends for
support doesn't exist. Is anyone maintaining it?
the GCCSDK, based on the sources at https://www.riscos.info/websvn/
A minor syntactical tweak to Makefile.unix notwithstanding, it seems to do
the right kinds of things, and
make -f Makefile.unix SCL=true install
puts the expected files into ~/gccsdk/env/...
If I then try to use it to compile an application (in this case WinEd from
the same source as above), then again it seems to do the correct sorts of
thing (except that WinEd's Makefile requires a lot of modification to make
it happy with the GCCSDK), but the process soon hits several problems.
The first, which I would like to sort out before moving on to the rest, is
that the DeskLib headers installed by the process above contain several
#include "DeskLib:Core.h"
lines and similar, which GCCSDK can't sensibly resolve. I can make things
build to a point where I'm looking at a handful of genuine-looking missing
or conflicting source files in WinEd by doing a search and replace to remove
the <DeskLib$Path> references from within ~/gccsdk/env/include/DeskLib/, but
this seems sub-optimal. Not least because the DeskLib docs refer to the
library being prepped for use in the GCCSDK, which suggests that this should
"just work". :-)
Is there some way to make GCCSDK happy with the files as they stand,
"DeskLib:Core.h" and the like included?
Also, where's the best place to ask about DeskLib nowadays. The last SVN
commit was 2012, and the Google Group that the documentation recommends for
support doesn't exist. Is anyone maintaining it?
--
Steve Fryatt
***@stevefryatt.org.uk
http://www.stevefryatt.org.uk/
Steve Fryatt
***@stevefryatt.org.uk
http://www.stevefryatt.org.uk/