Windows is the bastard child of operating systems in this regard, but a lot of APIs will accept forward slashes as well. On Windows, a file path looks like this: C:\Users\jsmith\Documents\file.txt On a Unix-like system (including Mac OS X and Linux), the same path would look like this: /home/jsmith/Documents/file.txt A URL, standardized in RFC 1738, … Read more
sed can use any separator instead of / in the s command. Just use something that is not encountered in your paths: s+AAA+BBB+ and so on. Alternatively (and if you don’t want to guess), you can pre-process your path with sed to escape the slashes: pwdesc=$(echo $PWD | sed ‘s_/_\\/_g’) and then do what you … Read more
The issue will be always present in Windows, to keep compatibility with old software. Use the NT-style name syntax “\\?\D:\very long path” to workaround this issue. In Windows 10 (Version 1607 – Anniversary Update) and Windows Server 2016 you seem to have an option to ignore the MAX_PATH issue by overriding a group policy entry … Read more
The whole point of making anything “canonical” is so that you can compare two things. For example, both ../../here/bar/x and ./test/../../bar/x may refer to the same location, but you can’t do a textual comparison on the two paths. However, if you turn them into their canonical representation, they both become ../bar/x, and we see that … Read more
To specify a directory to search for (binary) libraries, you just use -L: -L/data[…]/lib To specify the actual library name, you use -l: -lfoo # (links libfoo.a or libfoo.so) To specify a directory to search for include files (different from libraries!) you use -I: -I/data[…]/lib So I think what you want is something like g++ … Read more
For the folder name and drive, you can use: echo %~dp0 You can get a lot more information using different modifiers: %~I – expands %I removing any surrounding quotes (“) %~fI – expands %I to a fully qualified path name %~dI – expands %I to a drive letter only %~pI – expands %I to a … Read more
If you are using qmake, the standard Qt build system, just add a line to the .pro file as documented in the qmake Variable Reference: INCLUDEPATH += <your path> If you are using your own build system, you create a project by selecting “Import of Makefile-based project”. This will create some files in your project … Read more
Just like any other environment variable, with SET: SET PATH=%PATH%;c:\whatever\else If you want to have a little safety check built in first, check to see if the new path exists first: IF EXIST c:\whatever\else SET PATH=%PATH%;c:\whatever\else If you want that to be local to that batch file, use setlocal: setlocal set PATH=… set OTHERTHING=… @REM … Read more
Webpack does support multiple output paths. Set the output paths as the entry key. And use the name as output template. webpack config: entry: { ‘module/a/index’: ‘module/a/index.js’, ‘module/b/index’: ‘module/b/index.js’, }, output: { path: path.resolve(__dirname, ‘dist’), filename: ‘[name].js’ } generated: └── module ├── a │ └── index.js └── b └── index.js
I think your search for a “standard” naming convention will be in vain. Here are my proposals, based on existing, well-known programs: A) C:\users\OddThinking\Documents\My Source\Widget\foo.src — Vim calls it file root (:help filename-modifiers) B) C:\users\OddThinking\Documents\My Source\Widget\foo.src ——- file name or base name C) C:\users\OddThinking\Documents\My Source\Widget\foo.src ___ (without dot) file/name extension D) C:\users\OddThinking\Documents\My Source\Widget\foo.src ____ (with … Read more