Recent Posts

Pages: 1 2 3 4 [5] 6 7 8 9 10
Help / Re: Console does not display on Mac when running C code
« Last post by AndrewCot on June 22, 2022, 06:06:40 am »
Nothing you are doing is wrong as I can reproduce the issue.
Unfortunately at this point in time I cannot help as C++ source level debugging on the MacOS using GDB is not easy to get working due to Apple security changes a few releases ago and I have not successfully got GDB to work.
Help / Console does not display on Mac when running C code
« Last post by tjmulinazzi on June 22, 2022, 04:42:38 am »
I am new to C and when I try to just run hello world my terminal pops up and says:

'/Applications/ DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:. /Users/trajan/Desktop/test/bin/Debug/test '
trajan@Trajans-MacBook-Air ~ % '/Applications/ DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:. /Users/trajan/Desktop/test/bin/Debug/test '
zsh: no such file or directory: /Applications/ DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:. /Users/trajan/Desktop/test/bin/Debug/test

How can I get the console to pop up or what am I doing wrong?
Please help. Thanks!
Thanks for the post as it will help.

I looked at your repo's a long time ago and seen it was a few years old and did not spend allot of time figuring out how it worked. I will have another look and spend time figuring it out.
I did not see that MSYS2 has the lldb-vscode as I downloaded the official release for it from the src git repo and started it. I will switch to the MSYS2 version.
Plugins development / Re: LLDB debugger low level interface investigation results
« Last post by eranif on June 21, 2022, 01:11:35 am »
A quick update on this subject:

Since our chat here, I revived my 2 years old project "dbgd"

My goal was to create dap-gdb and dap-client, due to lack of time I paused my work on that.
Recently, I moved to develop full time on Mac and I needed a better lldb support (replacing my current lldb implementation which uses liblldb.dylib directly)

So with small effort I made dapcxx library that it built for wxWidgets.

All the interaction is done via events, i.e. whenever a an event / response arrives from the dap server, the GUI is notified via event (all the reads are done in a background thread)

You can check it out here: -> it is a complete standalone library with zero dependencies (other than wxWidgets)
It comes with a small UI that demonstrate how to use it

The DAP server initialization is done here:

You can install lldb-vscode from MSYS2 to try it out

Hope you will find it useful for your purposes

It is not intended to change behaviour of global variables.
It is intended to give the user a hint, what a global variable is and what the developer intended.

For example if you open the codeblocks project with a fresh installation the user is asked for two global variables: cb and wx31 (or whatever)
But the user has absolute no clue what to do with this variables or even with this dialog.

With this patch (this is only part one of a series of patches) the developer can store some information in the project file. For example it could store for the cb variable in the description field:
This variable is used to pass additional compiler flags to the build process of codeblocks. For example if you want to build a fast codeblocks installation pass -O3, but if you want build with debug information pass a -g to this variable
Now when the user opens the project file and codeblocks can not find the global variable 'cb' it will open a dialog with the description the developer provided.
If the variable is already defined nothing would happen. (Note that this described dialog is not part of this patch, i am currently working on it. This patch adds only the possibility for the developer to store additional description information to the project file)
 If the developer passes a default value this value will be suggested to the user. For the 'cb' variable the dev would provide -O3 and in the ask dialog -O3 would be provided. For the wx31 variable it would not make any sense to provide a default value, but you could provide a description what is like:
Point this path to installation directory of your wxWidgets 3.1 installation

Additionally it introduces ambiguity and unexpected behaviour.
Can you describe this a bit more? I can not find any ambiguity  or unexpected behaviour

Additionally, I have a patch pending that allows to manage environment variables at workspace level which may do what you want.

Workspace level setting of environment variables sounds very good to me. Never thought of that solution.

Tim S.
Sorry, but I am clearly against this patch. It spoils completely what global variables are for. Additionally it introduces ambiguity and unexpected behaviour.

What you have in mind can be achieved with environment variables instead and this functionality is already there. Including saving these settings in project files. Additionally, I have a patch pending that allows to manage environment variables at workspace level which may do what you want.

...unless you clearly specify a need that cannot be solved with existing options this patch will be rejected. Sorry.
Nightly builds / Re: The 19June 2022 build (12839) is out.
« Last post by Xaviou on June 20, 2022, 05:58:37 pm »

OS X version of this rev can be downloaded from my Google Drive.
There is a specific dmg file for versions 10.15 and 11.6 of the OS.
Note that these are not notarized versions of the application.

32 bits version for Windows can also be found in the same place.

Debian Buster and Bullseye (32 and 64 bits) can be installed from my repo.

If you have a branch on your github repo then I can pull the branch and test it when you want me to test the changes.

BTW I grabbed the rework/move_global_var_diag_to_src/1 branch yesterday and looked at it before I seen the ticket and post this morning (I am in Australia, +8hrs ahead of you at the moment as we have daylight saving, so in your winter I am 10 hrs ahead the same day).
Thank you for the fast feetback:
1) Yea, this is a huge problem, but i could not come up with a better name. I have to test if i can use new line in the header so i would call it "stored in project"? Any better idea for UI, naming?
2) Can do that.
3) Yea, i am not that familiar with wxWidgets so i have to look into it, was definitely on my todo list
4) This should already work over the "normal" global variables. When you load the project you should get a error message and the possibility to enter the variable. But i can add it somehow...
5) We do not know if the variable is used in a non loaded project, so why should be warn the user about it in this project?
6) This is a bug. Thanks i will fix it
7) The idea would be that "used" column should not be ticked, and probably in addition the row should be marked in yellow or red. But from 6. this seems to not work. Will have to look into it. Thanks!

a) I think this should simply be ignored. The default value should only be used if the variable is not defined. We probably could display it somehow in the global variable dialog, but i would not like to add some nagging UI for this. For example i use "ud" for compiling codeblocks. The default value would be "u" so i do  not want a error message every time i load he codeblocks project...
b) This could be added in a third step We probably could reuse this UI...
Pages: 1 2 3 4 [5] 6 7 8 9 10