Of course, my bad!
; PlatformIO Project Configuration File
;
; Build options: build flags, source filter
; Upload options: custom upload port, speed and extra flags
; Library options: dependencies, extra library storages
; Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; Redirecting...
[env:teensy35]
platform = teensy
board = teensy35
framework = arduino
build_flags = -O3
lib_extra_dirs = \\path_to_libraries_on_network_drive
monitor_port = COM[8]
monitor_speed = 115200
When I try to build the project I get lots of errors like this:
Compiling .pio\build\teensy35\src\utilities.cpp.o
'\\path_to_project_on_network_drive'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
arm-none-eabi-g++: error: src\control.cpp: No such file or directory
arm-none-eabi-g++: fatal error: no input files
compilation terminated.
'\\path_to_project_on_network_drive'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
arm-none-eabi-g++: error: src\logging.cpp: No such file or directory
arm-none-eabi-g++: error: src\mavlink_utilities.cpp: No such file or directory
arm-none-eabi-g++: error: src\main.cpp: No such file or directory
arm-none-eabi-g++: fatal error: no input files
compilation terminated.
Regarding whether or not I should be developing on network drives in my case its company policy that your work goes on the network drive. We do use source control for long standing projects as well. We do not have them on the drive so that multiple people can work on them, i definitely agree with you there! I think there are other use cases though, at a university or other large organisation personal files may be stored on a network drive for instance.
Thanks for your response