Hi Albert, I can't remember having changed something about paths, can you provide a revision for which it works ?
Cheers, Seb 2009/11/11 a.faber <[email protected]> > > Hi Seb, > I've experience similar problems as Rob, when I use the following setting > it > is OK > > set JALLIB_ROOT=pic\projects\jallib_svn > > but when using > > set JALLIB_ROOT=d:\pic\projects\jallib_svn > > I get the following errors > > Invalid board/test combination: [Error 3] The system cannot find the path > specif > ied: 'd/*.*' > Traceback (most recent call last): > File "d:\pic\projects\jallib_svn\tools\jallib.py", line 587, in > generate_sampl > es_for_board > generate_one_sample(board,test,fullsamplepath) > File "d:\pic\projects\jallib_svn\tools\jallib.py", line 541, in > generate_one_s > ample > status = do_compile([outfile],exitonerror=False,clean=True) > File "d:\pic\projects\jallib_svn\tools\jallib.py", line 200, in > do_compile > dirs = _explore_dir(d) > File "d:\pic\projects\jallib_svn\tools\jallib.py", line 116, in > _explore_dir > for fd in os.listdir(onedir): > WindowsError: [Error 3] The system cannot find the path specified: 'd/*.*' > > This problem is introduced a couple of weeks ago, before this it was > working > fine to use an absolute path with a drive letter. > > Albert > > > > > ----- Original Message ----- > From: "Sebastien Lelong" <[email protected]> > To: <[email protected]> > Sent: Wednesday, November 11, 2009 6:46 PM > Subject: [jallib] Re: generating samples from board/test files > > > > Hi Rob, > > > > > >> I think I may need some more help. > >> > > > > I think I need some more details... > > > > > > > >> > Finally again, reading generate_one_sample function it seems it can > >> > take > >> > a "deleteiffailed" argument. Set it to False and you should get your > >> > sample (yes you still have to modify code within jallib.py). > >> > >> I thought my test results were good enough to prepare for commit. > >> After I changed the device files in /jallib/include/device/ and some > >> board files in /jallib/test/board I ran (from /jallib/tools) > >> python jallib.py sample -a /jallib/sample > >> (this is the original jallib.py) > >> This creates a lot of console output and 88 more sample than were in > >> /jallib/sample before. When I compile all samples 71 of the new samples > >> have compile errors. What am I doing wrong? Why are there suddenly so > >> many more samples and how is it possible that so many of these do not > >> compile but still appear in /jallib/samples? > >> > > > > Are you sure you're running the original jallib.py (sorry to ask but > > sometime double-checking...) ? > > Then, "a lot of console output" is something you should post here, at > > least > > for one sample expecting to fail at compilation. Did you try to > explicitly > > generate a sample expecting to faile (with -t option IIRC) ? What's the > > result ? Ultimately I'd need all jal files involved (or enough I can play > > with) so I can reproduce here what you have. > > > > Cheers, > > Seb > > > > > > > > > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
