Hey, you only need to rebuild NOX the first time you introduce a new python component (after following the instructions on the wiki), so that the links are created to the build/src/ directory. After that, you can simply run NOX each time you edit your python component.
On Thu, Mar 31, 2011 at 11:32 PM, Bill Liao <[email protected]> wrote: > On Fri, Apr 1, 2011 at 5:29 AM, Kyriakos Zarifis <[email protected]> > wrote: > > Hi Karim, > > did you rerun ../configure and make after you edited configure.ac and > > Makefile.am? > > > > On Thu, Mar 31, 2011 at 7:42 AM, karim torkmen <[email protected] > > > > wrote: > >> > >> Hi, > >> I developed a component when I try to run it, I get the following error > >> message : > >> > >> **************************** > >> 00001|nox|INFO:Starting nox_core (/nox/build/src/.libs/lt-nox_core) > >> 00002|nox|DBG:Application installation report: > >> 00003|nox|DBG:built-in DSO deployer: > >> Current state: INSTALLED > >> Required state: INSTALLED > >> Dependencies: > >> > >> 00004|nox|DBG:built-in event dispatcher: > >> Current state: INSTALLED > >> Required state: INSTALLED > >> Dependencies: > >> > >> 00005|nox|ERR:Application 'try_topology' description not found. > >> *************************************** > >> To add my component I tried two methods: > >> The first one is through executing the script : nox-new-c-app.py > >> The second one is by editing meta.json, configure.ac and Makefile.am. > >> Unfortunately, none of them was able to make me run my component. > >> > >> Thank you for your help. > >> Regards, > >> Karim > >> > >> > >> _______________________________________________ > >> nox-dev mailing list > >> [email protected] > >> http://noxrepo.org/mailman/listinfo/nox-dev > > > > > > _______________________________________________ > > nox-dev mailing list > > [email protected] > > http://noxrepo.org/mailman/listinfo/nox-dev > > > > > > Hi, Kyriakos > Sorry to interrupt. But I'm wondering is it necessary to re-make > after building a new python component. > As far as I know after reading some source, there is no such > requirement right? > The python component is managed by PyRt, just as Dso-deployer. So, > for c++ component, maybe we should make to produce the *.so dynamic > library, but what will MAKE produce for new python component? > > Regards > wliao >
_______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev
