On 1/15/2023 4:38 AM, Alexander Grund via Cygwin wrote:
Hi,
consider the following MWE:
|$ touch bar/foo.h $ cat bar/main.cpp #include "foo.h" int main(){} With this most simple setup
calling GCC with `g++ "bar\main.cpp"` results in GCC failing to find the include file. However
using `g++ "ba
Alexander Grund via Cygwin writes:
> consider the following MWE:
>
> |$ touch bar/foo.h $ cat bar/main.cpp #include "foo.h" int main(){}
> |With this most simple setup calling GCC with `g++ "bar\main.cpp"`
> |results in GCC failing to find the include file. However using `g++
> |"bar/main.cpp"` wor
Am 15.01.2023 um 14:51 schrieb Hans-Bernhard Bröker via Cygwin:
Am 15.01.2023 um 13:38 schrieb Alexander Grund via Cygwin:
The build system, finding it is running on Windows, will pass paths
with backward slashes to the compiler.
And that's wrong. Cygwin is not, for practical intents and
Am 15.01.2023 um 13:38 schrieb Alexander Grund via Cygwin:
The build system, finding it is running on Windows, will pass paths with
backward slashes to the compiler.
And that's wrong. Cygwin is not, for practical intents and purposes,
Windows. It just runs on top of it.
Yes, backslashed
Hi,
consider the following MWE:
|$ touch bar/foo.h $ cat bar/main.cpp #include "foo.h" int main(){} With this most simple setup
calling GCC with `g++ "bar\main.cpp"` results in GCC failing to find the include file. However
using `g++ "bar/main.cpp"` works as expected. |
|So the compiler does f
5 matches
Mail list logo
