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
{{ message }}
This repository has been archived by the owner on Apr 5, 2024. It is now read-only.
Working on a cross platform project, it would be nice to set "Advanced Command Line Arguments" at the top level (Window|Preferences) to match the local installed environment. For example:
Must be set in each project, every time. These variables are already set in the Active Build Configuration. I would be happy to set these the same in all cases as cross compilation happens remotely, and the developer would not even have access to many of the otherwise references headers.
The text was updated successfully, but these errors were encountered:
You want to have global entry where you could configure this and then allow the project settings to take the global default?
Matching local environment will not work when targeting some remote/embedded cross-toolchain targets.
Maybe instead of a global, a per-configuration settings could be interesting? Not sure how much overhead it would create for users where they would have to configure it separately for each configuration in simple native projects.
My problem is that I need to set a group of -D values and every time I add a new project to eclipse the only place I can set them is in project cppcheclipse/advanced .... Even if I could set them in the manage profile settings somewhere. But this is a constant and ongoing issue... As it it I have 2 different configurations in there.On Apr 23, 2020 13:50, Anton Krug <[email protected]> wrote:
You want to have global entry where you could configure this and then allow the project settings to take the global default?
Matching local environment will not work when targeting some remote/embedded cross-toolchain targets.
Maybe instead of a global, a per-configuration settings could be interesting? Not sure how much overhead it would create for users where they would have to configure it separately for each configuration in simple native projects.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Working on a cross platform project, it would be nice to set "Advanced Command Line Arguments" at the top level (Window|Preferences) to match the local installed environment. For example:
-D'x86_64=1' -D'__linux=1' -D'__unix=1' -D'_POSIX_C_SOURCE=200112L'
Must be set in each project, every time. These variables are already set in the Active Build Configuration. I would be happy to set these the same in all cases as cross compilation happens remotely, and the developer would not even have access to many of the otherwise references headers.
The text was updated successfully, but these errors were encountered: