I'll speculate. Perhaps something changed in how GObject introspection
packages are built and installed between the time that sugar-runner and
sugar-toolkit-gtk3 were both supported, and the time now. If so, then commits
that change Makefile.am in sugar-toolkit-gtk3 may explain.
To not
James,
I am a novice with Make. I did look at the Make files for sugar-runner and
I found that Makefile.in had some lines reported as *Bad directive*:
@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)
/libsugarrunner_la-sugar-runner-window.Plo@am__quote@ # am--include-marker
Make sure the typelib has been installed correctly. Perhaps the install steps
are also bit rot.
Compare the steps against the SugarExt typelib installed by the
sugar-toolkit-gtk3 package.
In particular, I seem to recall an introspection scanner step is required, but
not sure if it is part of
My guess is SugarRunner is not in the Python Path, you'll have to confirm
and make sure it is.
--
Ibiam Chihurumnaya
ib...@sugarlabs.org
On Mon, Feb 19, 2024 at 4:47 PM James Simmons wrote:
> I've been preparing an old computer I just replaced as a gift for a bright
> eight year old boy
I've been preparing an old computer I just replaced as a gift for a bright
eight year old boy and his older brother. It will run Fedora 39. In
addition to the XFCE environment I want to give him a Sugar environment
with Activities.
In the process of setting this up I discovered that some of the
5 matches
Mail list logo
