Recent Posts

Pages: 1 ... 5 6 7 8 9 [10]
91
The libraries are intended for plugin developers, I removed them from the ZIP to reduce size.
 
92
I have uploaded here a zip containing the Codeblocks folder, you can use it as a portable application (no installation). This link will last 24 hours from now.

I am a C::B developer, the files are official and updated to revision 12857 (head-1).

Thanks for compiling and sharing that Win32 rev12857!
It seems to startup fine on Windows XP x86 with the mentioned drmingw-0.8.2 files, and it has the symbols browser. :)
Noted that the link will expire soon, I will keep it stored locally. 

(A minute ago I also found a similar Win32 package in google drive from Xaviou here:
https://forums.codeblocks.org/index.php/topic,25008.msg0/boardseen.html#new
Working too, but somehow it has all these .a libraries in the root of the program?)
93
I have uploaded here a zip containing the Codeblocks folder, you can use it as a portable application (no installation). This link will last 24 hours from now.

I am a C::B developer, the files are official and updated to revision 12857 (head-1).
94
Sadly, the version of Dr. MinGW used (0.9.1) does not run on XP-SP3, so the program will not start (I have just tried).

For the v20.03 release this incompatibility can be solved, or at least worked around, with the method posted by SiZiOUS here:
https://forums.codeblocks.org/index.php/topic,23770.0.html
Which comes down to using Dr. MinGW 0.8.2 binary files instead
95
Sadly, the version of Dr. MinGW used (0.9.1) does not run on XP-SP3, so the program will not start (I have just tried).
96
Hello AndrewCot,
Thanks for your efforts.
Me and some other guys at msfn.org  were discussing about the latest version of Code::Blocks able to run on Windows XP SP3 x86.
And unfortunately release v20.03 had the symbols browser disabled on purpose. Making release release v17.12 the most viable option. It would be interesting to try your unofficial x86 SVN, to see if it has a proper symbols browser. But I cannot try it, because this link does not work anymore...:
https://sourceforge.net/projects/unofficial-cb-installers/
Please advise.
97
General (but related to Code::Blocks) / Re: No dark mode?
« Last post by Krice on August 04, 2022, 07:01:54 am »
Can anybody actually work like this??

Yes. In fact I can only use light themes which is strange I guess. I like dark and also solarized themes, they look cool, but my eyes hurt if I try to use them. I have a long, long background in programming. I started with 8- and 16-bit computers back in 1980's and those had "dark" themes by default, although some computers like Commodore 64 has blue background. Then I got PC and used Turbo C++ default for years, it also has a dark blue background. But now I can't use anything else than light themes. My monitor settings are also not typical I think, I barely have any brightness, it's on very low value. That's how you don't have to stare at bright screen which is bad for your eyes anyway. Some people just blast the brightness and contrast settings through the roof, I don't know why.
98
Plugins development / Re: error alert message when using ThreadSearch Plugin
« Last post by Miguel Gimenez on August 03, 2022, 11:52:01 am »
Thank you for testing (I could not reproduce the issue).

I have just marked ticket 1275 as fixed.
99
Plugins development / Re: DAP debug plugin testing
« Last post by AndrewCot on August 03, 2022, 11:35:05 am »
I would read the following doc for my install notes:To distribute it on a release there is allot of work that needs to be done, such as the following:
  • The Windows NSIS installer is missing all of the new files/changes/updates since the 20.03 and I have given up trying to get my NSIS updates included as it is way too hard and would take me way too much of my time to explain every change I made in the NSIS script (the existing installer has two NSIS scripts that have been merged into one that uses a parameter to build either a 32 or 64 bit installer)
  • As per a previous email someone would need to run with getting the source into the CB SF tree
  • Someone would need to either update the existing projects to use global variables for all three OS's and hook up the new plugin project files into the workspaces. This assumes that some one  has merge in the MAC workspace and project files that do not exist at the moment (there is a SF ticket for this, but no one has looked at it). This way all three workspace's have the plugin.
  • Someone would need to update the make process to incorporate the plugin makefile.am and include the zip & two DLL's into the output files.
  • Someone would need to update the WIKI page for the new DAP plugin.
  • If you want the DAP debugger automatically detected and added in then you will need other changes (there is a SF ticket for the base work). There are additional changes for the DAP debugger in the clang compiler XML file and a few additional changes as the DAP debugger is not GDB.
  • The biggest one for other devs to test it on various MAC's. Testing on Windows and Linux is not where the DAP plugin will be used the most as there is no GDB DAP debugger available and the LLDB debugger on Windows may not be feature complete compared to the MAC version. I do not know the status of the Linux version, but would assume it's between the other two.
  • There is one or two minor (few lines) other changes needed in the SF truck if you just want to try the plugins, but I cannot remember what they were as I did them a while ago. They will cause a link fail or some debugging feature to fail.
My repo has all of the items with exception of the MAC testing in the list above. I do not have time to back port the plugin to work with the stock SF source tree. I will take the time to go over my SF tickets based on the oldest chronological order first as my source tree is based on all of the tickets I have entered in SF with the exception of this DAP work.

100
Plugins development / Re: DAP debug plugin testing
« Last post by BlueHazzard on August 03, 2022, 09:52:42 am »
Thank you  a lot for your work!!!
I will test as soon as possible.

On a side note: Do you have any idea how we can distribute this on a release? On windows we probably have to provide the language server executables? (The same for the language server code completion i guess?) On linux we could probably depend on some packages?
Pages: 1 ... 5 6 7 8 9 [10]