Showing registers, and broken debugger output

General questions regarding the usage of CodeLite
DavidGH
CodeLite Plugin
Posts: 585
Joined: Wed Sep 03, 2008 7:26 pm
Contact:

Re: Showing registers, and broken debugger output

Post by DavidGH » Tue Jun 03, 2014 12:33 pm

Hi,
as he builds and packages for all Linux distros
Not quite all ;) .
I have to decide to upgrade to 14.04 or stick with it
You do have a third option: CodeLite isn't hard to build from source...

Regards,

David

ghost
CodeLite Enthusiast
Posts: 20
Joined: Wed May 28, 2014 9:58 pm
Genuine User: Yes
IDE Question: C++
Contact:

Re: Showing registers, and broken debugger output

Post by ghost » Tue Jun 03, 2014 12:49 pm

Hi, I think I will upgrade my VMs to 14.04 then.
If I stick with 12.04, building from source now will mean re-building on each new release... I prefer to stay on a "supported" distro to get future upgrades.
Many thanks
Bye

ghost
CodeLite Enthusiast
Posts: 20
Joined: Wed May 28, 2014 9:58 pm
Genuine User: Yes
IDE Question: C++
Contact:

Re: Showing registers, and broken debugger output

Post by ghost » Tue Jun 03, 2014 10:33 pm

Just for curiosity, why is Ubuntu 14.04 still sticking with codelite 2.8 ?
The same for debian (even if I noticed that in experimental appeared the 5.4).

I also noticed you put lldb etc. as "recommeds" in ubuntu package; this by default triggers their installation, I think it would be better to remove it, as most people do not need it unless they know what it that......

Thanks
Bye

User avatar
eranif
CodeLite Plugin
Posts: 5934
Joined: Wed Feb 06, 2008 9:29 pm
Genuine User: Yes
IDE Question: C++
Contact:

Re: Showing registers, and broken debugger output

Post by eranif » Tue Jun 03, 2014 10:40 pm

ghost wrote:Just for curiosity, why is Ubuntu 14.04 still sticking with codelite 2.8 ?
Probably because up until now, wxWidgets 3.0 was not in their repos.

We switched to wx3.0 2 years ago ( I think ) - when all distros only had wx2.8
this is why we provide our own repository for Linux (when I say "we" I mean "David" ;))
ghost wrote:I also noticed you put lldb etc. as "recommeds" in ubuntu package; this by default triggers their installation
lldb is needed for the LLDBDebugger plugin. I think that the package name is lldb-3.5-dev or something like this

Eran
Make sure you have read the HOW TO POST thread

DavidGH
CodeLite Plugin
Posts: 585
Joined: Wed Sep 03, 2008 7:26 pm
Contact:

Re: Showing registers, and broken debugger output

Post by DavidGH » Tue Jun 03, 2014 11:45 pm

why is Ubuntu 14.04 still sticking with codelite 2.8 ?
We switched to wx3.0 2 years ago ( I think ) - when all distros only had wx2.8
They didn't update in our wx2.8 days either. I think it's more likely that nobody was maintaining it.
I also noticed you put lldb etc. as "recommeds" in ubuntu package; this by default triggers their installation, I think it would be better to remove it, as most people do not need it unless they know what it that......
It's a problem. lldb and libedit-dev (yes, I really do mean -dev) are needed at runtime for the new codelite-lldb binary. Without them it fails to run, without giving any reason. For people who are actually going to use lldb, I should have made them 'requires'; but that's not fair on those who will never try it. 'recommends' is a compromise (so it will please nobody ;) ).

ghost
CodeLite Enthusiast
Posts: 20
Joined: Wed May 28, 2014 9:58 pm
Genuine User: Yes
IDE Question: C++
Contact:

Re: Showing registers, and broken debugger output

Post by ghost » Tue Jun 03, 2014 11:53 pm

Well, now that libwx 3.0 is in Ubuntu maybe contacting that mantainer of the package could be worthwhile, if you are interested in it.

About lldb, I installed codelite with
apt-get install --no-install-recommends codelite
so lldb, llvm and friends were not installed, and I have no problems at all using standard gcc/gdb.

So probably they could be marked as "suggests" instead of "recommends", even if nowadays 130 MB more are not a problem :-)

Post Reply