Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

complie of irteus/*.l does not run after compile_*.log is generated. #374

Closed
snozawa opened this issue May 8, 2016 · 4 comments
Closed

Comments

@snozawa
Copy link
Contributor

snozawa commented May 8, 2016

After #373, build behaviour changed because of change of build dependency.
Complie of irteus/xx.l does not run after compile_xx.log is generated.

  • Reproduce the problem
$ cd ~/ros/indigo_parent/src/Euslisp/jskeus/irteus
$ touch irtmodel.l
$ make
make: Nothing to be done for `all'.

The same problem occurs when i run catkin bt in jskeus directory.
If I remove compile_xx.log file, compile of irteus/xx.l starts.

  • Expected behaviour
    compile_irtg.l is called invoked by irtmodel.l time-stamp update.
@k-okada
Copy link
Member

k-okada commented May 8, 2016

sorry, check if #375 fixes

@k-okada
Copy link
Member

k-okada commented May 8, 2016

see euslisp/EusLisp#177 for euslisp case

@snozawa
Copy link
Contributor Author

snozawa commented May 8, 2016

Thanks!
BTW, in the original version,

$(IRTEUSOBJS):
    $(BINDIR)/eus2$(ESFX) "(setq *objdir* \"$(INSTALLOBJDIR)/\")" < ./compile_irt.l > /dev/null

dependencies are not written explicitly, but it worked correctly.
Which part specifies dependency?

@k-okada
Copy link
Member

k-okada commented May 9, 2016

see
https://github.com/euslisp/EusLisp/blob/master/lisp/Makefile.generic2#L49
and
https://github.com/euslisp/EusLisp/blob/master/lisp/Makefile.generic2#L442

◉ Kei Okada

On Mon, May 9, 2016 at 8:56 AM, Shunichi Nozawa [email protected]
wrote:

Thanks!
BTW, in the original version,

$(IRTEUSOBJS):
$(BINDIR)/eus2$(ESFX) "(setq objdir "$(INSTALLOBJDIR)/")" < ./compile_irt.l > /dev/null

dependencies are not written explicitly, but it worked correctly.
Which part specifies dependency?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#374 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants