[Sugar-devel] Sugar-build : can't see my own activity

[laurent bernabe]

no it is a pygame activity built upon sugar olpc games


2013/9/14 Daniel Narvaez <dwnarvaez at gmail.com>

> Is it a gtk2 activity? If not, is it using "from sugar3.activity import
> bundlebuilder" in the setup.py?
>
>
> On 14 September 2013 22:06, Daniel Narvaez <dwnarvaez at gmail.com> wrote:
>
>> From terminal is fine, you are  inside the chroot. Looks like a bug
>> somewhere, investigating...
>>
>>
>> On 14 September 2013 22:03, laurent bernabe <laurent.bernabe at gmail.com>wrote:
>>
>>> I don't think, as I started the sugar emulator with
>>> $> ./osbuild run
>>>
>>> rather than running $> ./osbuild shell
>>>
>>> And from the terminal activity, I enter the installation command for my
>>> own activity.
>>>
>>>
>>> 2013/9/14 Daniel Narvaez <dwnarvaez at gmail.com>
>>>
>>>> Did you run setup.py dev inside an osbuild shell? (Btw I don't develop
>>>> activities myself so your feedback is very useful)
>>>>
>>>> On Saturday, 14 September 2013, laurent bernabe wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I've just installed my own activity in sugar-build, by the command
>>>>> $>python setup.py dev
>>>>>
>>>>> But, though I've restarted Sugar-build, I can't see my own
>>>>> application, even looking at the table view of the activities. And I did
>>>>> not see any trace of my own activity in the logs.
>>>>>
>>>>> Meanwhile, I launched "$> python setup.py dev" again, and I got the
>>>>> message "the activity is already installed in developpement mode".
>>>>>
>>>>> Also, I looked into the sugar-build folder, but did not see the
>>>>> subfolder activities, letting me think that the application is not properly
>>>>> installed.
>>>>>
>>>>> What did I misunderstood ?
>>>>>
>>>>> Regards
>>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Narvaez
>>>>
>>>>
>>>
>>
>>
>> --
>> Daniel Narvaez
>>
>
>
>
> --
> Daniel Narvaez
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130914/d5c6be82/attachment-0001.html>