You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a way to allow setting arbitrary compiler and linker flags, on an OS-specific basis.
For example, a problem arises if we have this command: (just an example, this isn't actual syntax)
$ qb --cflag "-O3"
Which will work okay on gcc/clang, but won't work on MSVC.
I think a lot of common flags can be added natively with the proper abstractions built-in (the -O3 example above already can be done with --optimize), but for the few cases that we do want to set flags, it could be nice to do so.
Perhaps this would best be done in the config file alone. Here's a possible thought:
[windows]
cflags = "/O2"
[linux]
cflags = "-O3"
But this raises some questions about what we can put exactly in these [windows] and [linux] blocks, which should probably be limited in scope to avoid confusion. Maybe we can even be more explicit in our intent: [compiler.windows].
The text was updated successfully, but these errors were encountered:
We need a way to allow setting arbitrary compiler and linker flags, on an OS-specific basis.
For example, a problem arises if we have this command: (just an example, this isn't actual syntax)
Which will work okay on gcc/clang, but won't work on MSVC.
I think a lot of common flags can be added natively with the proper abstractions built-in (the
-O3
example above already can be done with--optimize
), but for the few cases that we do want to set flags, it could be nice to do so.Perhaps this would best be done in the config file alone. Here's a possible thought:
But this raises some questions about what we can put exactly in these
[windows]
and[linux]
blocks, which should probably be limited in scope to avoid confusion. Maybe we can even be more explicit in our intent:[compiler.windows]
.The text was updated successfully, but these errors were encountered: