daves Posted April 4, 2014 Share Posted April 4, 2014 I tried to include usrcode.c in an existing mature project and now I get Build Process For usralgo.ko has started. C:\ABD\PowerPMAC\SPMM\Phase2\Phase2\Phase2.ppproj(311,5): Error : fixdep: /cygdrive/c/ABD/POWERP~1/SPMM/Phase2/Phase2/CLANGU~1/REALTI~1/../../PMAC\: No such file or directory Build Process For usralgo.ko has ended. in Release or Debug builds. What do I need to edit to fix this path error? Link to comment Share on other sites More sharing options...
steve.milici Posted April 4, 2014 Share Posted April 4, 2014 To instruct the Power PMAC to use a compiled and downloaded user-written phase routine, rightclick on “Realtime Routines” in the “C Language” branch. Select “User Servo Setup” to get the window permitting you to assign user routines to motors. If you have not added your routine’s name to the list of selectable routines, click on “Add New Function”, type your routine name into the dialog box, and click on “Apply”. Link to comment Share on other sites More sharing options...
daves Posted April 7, 2014 Author Share Posted April 7, 2014 I had done that. I'm not sure how that error message could be related to that. Anyway, turns ot it was the following line: #include "../../PMAC Script Language/Global Includes/common globals.pmh" It seems the build procedure cannot handle spaces in paths. This is a major problem for me as I need to include this file in my C-code (don't worry the script language part is not included thanks to #ifdef) Link to comment Share on other sites More sharing options...
StephenJ Posted April 7, 2014 Share Posted April 7, 2014 Hi Dave Try: #include "../../PMAC\ Script\ Language/Global\ Includes/common globals.pmh" Link to comment Share on other sites More sharing options...
daves Posted September 1, 2014 Author Share Posted September 1, 2014 That doesn't work. And the correct way doesn't work on the latest 1.7.0.53/1.6.1.1 either. I found this works but it is not great: #include "../../PMACSC~1/GLOBAL~1/COMMON~2.PMH" Maybe this can help you figure out what is wrong in the build command. Link to comment Share on other sites More sharing options...
Recommended Posts