I'm sure there is probably a work around/alternative but i was just hoping

is it possible to allow separation of library paths for the includes? I'm sure most of us use Xander's lib, but I would also like to have my own common library as well. being able to specify both, semi-colon delimited or similar, would be helpful.

as it is now (3.512 pre) there is a user 'include' file for platform, as well as a user include files (common) - so I guess i can use both of those for this, however, just semi separated single entry is more in line with what I'm used to, and to me, more logical.

where "Directory" is a folder in the same folder that your source file is located.

"../" (up one directory) and "./" are alsoerecognized in the file path for relative file references. Multiple folders can be specified in the name -- "./directory/subdirectory/filename"

You can also specify non-relative (i.e. absolute file names) with

Code:

#include "C:/folderName/filename.h"

Mon Oct 15, 2012 3:45 pm

Spiked3

Expert

Joined: Tue Feb 28, 2012 3:10 pmPosts: 197

Re: multiple includes

I see what you are saying.

In my case I keep other peoples code very separate from mine, for VCS reasons. I could still move directories around to make this usable (it wouldnt by any chance support environment variables would it? I have not checked), but like I said, was just hoping a change to the compiler so that I could make a single change to a setting in the IDE was easy enough (and more in line with ANSI C ) as compared to changing/managing include lines in many programs. Maybe at some later point, it is not creating any problems at the moment.

I agree. I would like this feature as well. Since there are different versions of RobotC, different versions of Xander's Driver Suite as well as different versions of our FTC library, I found myself having all these in different folders to test the code. It would be nice to be able to switch the "include path" to point to different versions of the library instead of going into code and change the path of each include. Or worst yet, duplicate the library in another folder so that it is at a fixed relative path (e.g. ..\MyLib). Well, nice to have but not high priority.

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum