[Sugar-devel] Advice needed on sugar-runner

[James Simmons]

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 at ./$(DEPDIR)
/libsugarrunner_la-sugar-runner-window.Plo at am__quote@ # am--include-marker

@AMDEP_TRUE@@am__include@ @am__quote at ./$(DEPDIR)
/libsugarrunner_la-sugar-runner.Plo at am__quote@ # am--include-marker


$(am__depfiles_remade):

@$(MKDIR_P) $(@D)

@echo '# dummy' >$@-t && $(am__mv) $@-t $@


am--depfiles: $(am__depfiles_remade)


.c.o:

@am__fastdepCC_TRUE@ $(AM_V_CC)$(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*
.Tpo -c -o $@ $<

@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po

@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='$<' object='$@'
libtool=no @AMDEPBACKSLASH@

@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
@AMDEPBACKSLASH@

@am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(COMPILE) -c -o $@ $<


.c.obj:

@am__fastdepCC_TRUE@ $(AM_V_CC)$(COMPILE) -MT $@ -MD -MP -MF $(DEPDIR)/$*
.Tpo -c -o $@ `$(CYGPATH_W) '$<'`

@am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/$*.Tpo $(DEPDIR)/$*.Po

@AMDEP_TRUE@@am__fastdepCC_FALSE@ $(AM_V_CC)source='$<' object='$@'
libtool=no @AMDEPBACKSLASH@

@AMDEP_TRUE@@am__fastdepCC_FALSE@ DEPDIR=$(DEPDIR) $(CCDEPMODE) $(depcomp)
@AMDEPBACKSLASH@

@am__fastdepCC_FALSE@ $(AM_V_CC at am__nodep@)$(COMPILE) -c -o $@ `$(CYGPATH_W)
'$<'`


The ones with red underlines are the ones. The generated Makefile does not
report any errors.


I'm going to try generating a Makefile for sugar-toolkit-gtk3 and see if
that suggests anything.


Thanks.


James Simmons

On Mon, Feb 19, 2024 at 1:42 PM James Cameron <quozl at laptop.org> wrote:

> 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 "make install" or if it fails if the tool is
> not installed.
>
> On Mon, Feb 19, 2024 at 09:47:36AM -0600, James Simmons wrote:
> > 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
> Activities I
> > wrote years ago have succumbed to bit rot and needed updating. I was
> able to do
> > this, but I was disappointed to find that I could not use sugar-runner
> to run
> > the Sugar environment in a window because it had not been maintained.
> >
> > I thought I'd take a stab at getting sugar-runner working. I checked out
> the
> > project, installed all the dependencies autogen.sh asked for, updated the
> > scripts to use python3, then ran what looked to be a successful make and
> sudo
> > make install. Then I tried to run
> >
> > sugar-runner
> >
> > and I got these Python errors:
> >
> > jamessimmons at unknownF4390913EB01:~$ sugar-runner
> > Traceback (most recent call last):
> >   File "/usr/local/bin/sugar-runner", line 28, in <module>
> >     gi.require_version('SugarRunner', '1.0')
> >   File "/usr/lib64/python3.12/site-packages/gi/__init__.py", line 126, in
> > require_version
> >     raise ValueError('Namespace %s not available' % namespace)
> > ValueError: Namespace SugarRunner not available
> >
> > At this point I'm stuck. If any of you have any suggestions on how to
> proceed
> > I'd love to hear them.
> >
> > Thanks,
> >
> > James Simmons
> >
>
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20240219/ddbb30d9/attachment-0001.htm>