Difficulty building RTAI linuxcnc from source

As far as I can tell, I am successfully building the LinuxCNC project. Make runs without error. From linuxcnc-dev/src I do sudo make setuid. Then I cd up one level and from linuccnc-dev I do ./scripts/rip-environment linuxcnc. The software runs, I choose the Motenc interface, the software sees the Vital Systems interface card (because I bought an old desktop with legacy PCI slots), and I get the GUI. I've connected a motor and encoder to the first axis on the interface card. When I twist the motor shaft, I see X axis position change on the GUI. All this is wonderful progress.
What concerns me is that for some reason linuxcnc is taking its configuration values not from the configs folder under linuxcnc-dev but instead from the configs folder under my compiled-by-LinuxCNC.org version.

southbayguy wrote:

What concerns me is that for some reason linuxcnc is taking its configuration values not from the configs folder under linuxcnc-dev but instead from the configs folder under my compiled-by-LinuxCNC.org version.

That is normal.

Thank you for writing back.
I want to re-state things to make sure I'm clear.
From LinuxCNC.org, I downloaded the ready-to-run linuxcnc. It is in its own folder, at /home/robert/linuxcnc. Under that folder, there are two more folders, called configs and nc_files.
Under configs, there is a folder called by_interface.vitalsystems.
Within that last directory, there is a file called motenc.ini.
So the complete path is /home/robert/linuxcnc/configs/by_interface.vitalsystems/motenc.ini.

I also wanted to be able to build from source. I made a directory called linuxcnc-dev and put it under home/robert. So linuxcnc and linuxcnc-dev are actually at the same level.
To drill down to motenc.ini within linuxcnc-dev, the path is a tiny bit different. It's /home/robert/linuxcnc-dev/configs/by_interface/vitalsystems/motenc.ini.
The reading I did about building from source and running from the run-in-place environment seemed to say that it was a self-contained system, independent of other software installed on the machine. I find it confusing -- in that context -- that when I'm running the home-built version of linuxcnc it doesn't stay within the linuxcnc-dev folder for its configuration values.

You might have several experimental RIP configs for the one configuration.
You may also still be using the .Deb versions while compiling some experimental feature and swapping to and from b closing windows and running  the script
Normally, you would open the linuxcnc-dev config from the chooser and it asks you if you want to copy the config into ~/linuxcnc/configs where it belongs
If you revisit the building Linuxcnc docs, you may like to explore building the Debs and installing with dpkg -i
I ran RIP for years before trying this and it is very convenient as it creates the CNC Menu. When configuring adding no-docs  to the command line will save a few hours by skipping building the Debs for the docs.

Thank you.
I still don't understand what I need to do to make my home-built version of linuxcnc go to

/home/robert/linuxcnc-dev/configs/by_interface/vitalsystems/motenc.ini.

for its configuration values.

southbayguy wrote:

Thank you.
I still don't understand what I need to do to make my home-built version of linuxcnc go to

/home/robert/linuxcnc-dev/configs/by_interface/vitalsystems/motenc.ini.

for its configuration values.

You don't! You make a copy in /home/robert/linuxcnc/configs by selecting these options.

 

Then it will appear under the chooser under My configurations.
Then you edit the configuration you have created in /home/robert/linuxcnc/configs

IF you look at the chooser, it says Sample Configurtations at the top of the Vital tree, They are not designed to be edited in situ.