Tony wrote:
> "profiling.c" and "profiling.pro" should be "profiler.c" and > "profiler.pro" respectively. I'll correct that in the text. > If (like me) you're compiling in a shadow > directory, you must link profiler.c, not profiling.c, from the > shadowdir to its parent, i.e. (the shadow directory being current, and > assuming a Unix-like OS) > > ln -sv ../profiler.c "make shadow" takes care of that, right? Or does that not work if the directory already exists? I suppose that never worked then. > profiler.pro will be linked automatically by virtue of the link proto > -> ../proto in the src directory. -- Save the plankton - eat a whale. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201907141255.x6ECtw04017760%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
