Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Code::Blocks live svn ebuild - Part 2
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Mon Nov 26, 2007 6:29 pm    Post subject: Reply with quote

XavierMiller wrote:
keenblade wrote:
Yes, thats great. C::B compiles fine, but it seems autorevision needs a fix again. :)


Oh yes... did the C::B dev change something that need a new ebuild ?

It seems like. I forgot that. Now I'm into it.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8270
Location: ~Brussels - Belgique

PostPosted: Mon Nov 26, 2007 7:37 pm    Post subject: Reply with quote

not so important, but thank you for maintaining even for little details :D
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Tue Nov 27, 2007 3:26 am    Post subject: Reply with quote

XavierMiller wrote:
not so important, but thank you for maintaining even for little details :D

Thanks. It is great to know that this has some use for a gentoo user other than me. I love this community.
Now autorevision works. C::B displays not only revision number, but also revision date and time correctly.
Please redownload it.
Do you think the ebuild needs revision bump to r18, for a little fix like this? Or is ok only referring the date in change log like what I do?
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8270
Location: ~Brussels - Belgique

PostPosted: Tue Nov 27, 2007 6:39 pm    Post subject: Reply with quote

and what about wxGTK-2.8 that is appearing in portage ?
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Tue Nov 27, 2007 7:19 pm    Post subject: Reply with quote

XavierMiller wrote:
and what about wxGTK-2.8 that is appearing in portage ?

It is about to hit the portage according to this. May be we can switch to wxGTK-2.8.7, if C::B devs say good things about it (or skip it like 2.8.5).
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"


Last edited by keenblade on Tue Nov 27, 2007 8:05 pm; edited 1 time in total
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8270
Location: ~Brussels - Belgique

PostPosted: Tue Nov 27, 2007 7:49 pm    Post subject: Reply with quote

meanwhile, I emerged C::B 4680 with wxGTK-2.8.7 (your ebuild using wxGTK, not wxPyhon) and it seems ok :)

Next step: wait until wxGTK-2.8 will be unmasked :D
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8270
Location: ~Brussels - Belgique

PostPosted: Thu Nov 29, 2007 5:57 pm    Post subject: Reply with quote

Hello,

I emerge and run C::B with portage version of wxGTK (locally updated to 2.8.7 using wxGTK sources and not wxPython) ebuilds and eclasses :D (unmasked)

So you need only the C::B ebuild 8)
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Fri Nov 30, 2007 2:11 am    Post subject: Reply with quote

XavierMiller wrote:
Hello,

I emerge and run C::B with portage version of wxGTK (locally updated to 2.8.7 using wxGTK sources and not wxPython) ebuilds and eclasses :D (unmasked)

So you need only the C::B ebuild 8)

That's great. I see wxGTK-2.8.6.1 in portage. I'll try to update locally to 2.8.7, just like you. If it works, I'll include it in the overlay.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8270
Location: ~Brussels - Belgique

PostPosted: Fri Nov 30, 2007 7:50 am    Post subject: Reply with quote

oh, I ran too fast : the C::B ebuild needs to be updated because wxGTK-2.8* doesn't have the unicode USE flag anymore...

EDIT: after a really dirty edit of the C::B ebuild (forcing unicode flag), it works, but a Q/A notice tells my ebuild doesn't use a "unicode" IUSE
Quote:
* QA Notice: USE Flag 'unicode' not in IUSE for dev-util/codeblocks-9999-r17

_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
rhill
Retired Dev
Retired Dev


Joined: 22 Oct 2004
Posts: 1629
Location: sk.ca

PostPosted: Sun Dec 02, 2007 12:55 am    Post subject: Reply with quote

i'll be bumping to wxGTK-2.8.7 this weekend. if you guys run into any problems using it or the wxwidgets.eclass in the tree, please let me know. i'd rather find out now, before i unmask it.
_________________
by design, by neglect
for a fact or just for effect
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Sun Dec 02, 2007 8:45 am    Post subject: Reply with quote

dirtyepic wrote:
i'll be bumping to wxGTK-2.8.7 this weekend. if you guys run into any problems using it or the wxwidgets.eclass in the tree, please let me know. i'd rather find out now, before i unmask it.

wxGTK-2.8.6.1 in portage does not have unicode useflag. Is there any specific reason for that? Because we have this die message:
Code:
x11-libs/wxGTK-2.8.6.1 does not actually support the unicode USE flag!

After wxGTK-2.8.6.1 in portage works, I'll test wxGTK-2.8.7.x

XavierMiller wrote:
oh, I ran too fast : the C::B ebuild needs to be updated because wxGTK-2.8* doesn't have the unicode USE flag anymore...

EDIT: after a really dirty edit of the C::B ebuild (forcing unicode flag), it works, but a Q/A notice tells my ebuild doesn't use a "unicode" IUSE
Quote:
* QA Notice: USE Flag 'unicode' not in IUSE for dev-util/codeblocks-9999-r17

XavierMiller, problem is not c::B ebuild, but wxGTK ebuild in portage (which does not have unicode useflag).
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
moesasji
Apprentice
Apprentice


Joined: 10 May 2005
Posts: 263

PostPosted: Sun Dec 02, 2007 9:52 am    Post subject: Reply with quote

keenblade wrote:
wxGTK-2.8.6.1 in portage does not have unicode useflag. Is there any specific reason for that?


There was a post on planet-Gentoo about this....see here for the direct link to the blog of the maintainer. Basically wxGTK is moving towards UTF8 for the next release (wxGTK3). Combined with the fact that getting wxGTK in the tree seems to be a nightmare the maintainer decided to drop ansi/unicode support. Probably to reduce the amount of weird bug-reports....

ps) Due to the same reason he also decided to drop support for having both debug and release version around. A shame, but understandable if he is the only one taking care of it.
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Sun Dec 02, 2007 10:48 am    Post subject: Reply with quote

moesasji wrote:
keenblade wrote:
wxGTK-2.8.6.1 in portage does not have unicode useflag. Is there any specific reason for that?


There was a post on planet-Gentoo about this....see here for the direct link to the blog of the maintainer. Basically wxGTK is moving towards UTF8 for the next release (wxGTK3). Combined with the fact that getting wxGTK in the tree seems to be a nightmare the maintainer decided to drop ansi/unicode support. Probably to reduce the amount of weird bug-reports....

Currently we have both ansi and unicode support with split ebuild (the one in portage). Later ansi support will be removed. The current ebuild has the unicode support, but just needs unicode useflag in the section.
Code:

IUSE="unicode"

Then wxGTK and C::B emerge just fine.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
rhill
Retired Dev
Retired Dev


Joined: 22 Oct 2004
Posts: 1629
Location: sk.ca

PostPosted: Mon Dec 03, 2007 4:41 am    Post subject: Reply with quote

keenblade wrote:
wxGTK-2.8.6.1 in portage does not have unicode useflag. Is there any specific reason for that? Because we have this die message:
Code:
x11-libs/wxGTK-2.8.6.1 does not actually support the unicode USE flag!

After wxGTK-2.8.6.1 in portage works, I'll test wxGTK-2.8.7.x


well because unicode is the only option now, there's no USE flag. i'm not sure exactly what you're asking for.
_________________
by design, by neglect
for a fact or just for effect
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8270
Location: ~Brussels - Belgique

PostPosted: Mon Dec 03, 2007 6:48 am    Post subject: Reply with quote

so we need to force unicode in C::B (as I did)?
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2277
Location: Bardowick, Germany

PostPosted: Mon Dec 03, 2007 2:13 pm    Post subject: Reply with quote

Could unicode be the problem why c::b compiles well on one machin (has unicode support) and on the other it doesn't, where I do not have unicode support?

On the machine in question I can't use unicode, because I am using an ext2/3 partition to store data for use with linux and windows. The windows ext2 drivers unfortunately do not support unicode. :( I wouldn't fancy to "go back" to FAT32, but if I have to... well...

btw.:
I found out, that the variable "Code", mentioned above, is of type "wxString", which is declared in string.h in wxGTK (2.6/2.8). In wxChar.h, version 2.8, there is a "typedef wchar_t wxChar", so the error message mentioned implies, that the wrong version of "wxChar.h" is used. That's very curious, as the beginning of the emerge states, that exGTK 2.8 (ANSI version) is used... And on at least one point, wxGTK 2.8 was the only version installed...

But I am compiling c::b right now with USE="-contrib" again, so I can track the issue again on the machine in question. Fortunately SVN provides .workspace files, and the "Find declaration/implementation" feature of codeblocks works like a charm!

Edith had to say:
I am a bit confused now. wxChar.h states:
Code:
    /* GNU libc has __WCHAR_TYPE__ which requires special treatment, see */
    /* comment below */
    #if !defined(__WCHAR_TYPE__) || \
        (!defined(__GNUC__) || wxCHECK_GCC_VERSION(2, 96))
        /* standard case */
        typedef wchar_t wxChar;
        typedef wchar_t wxSChar;
        typedef wchar_t wxUChar;
    #else /* __WCHAR_TYPE__ and gcc < 2.96 */
        /* VS: wxWidgets used to define wxChar as __WCHAR_TYPE__ here. However, */
        /*     this doesn't work with new GCC 3.x compilers because wchar_t is */
        /*     C++'s builtin type in the new standard. OTOH, old compilers (GCC */
        /*     2.x) won't accept new definition of wx{S,U}Char, therefore we */
        /*     have to define wxChar conditionally depending on detected */
        /*     compiler & compiler version. */
        /*     with old definition of wxChar. */
        typedef __WCHAR_TYPE__ wxChar;
        typedef __WCHAR_TYPE__ wxSChar;
        typedef __WCHAR_TYPE__ wxUChar;
    #endif /* __WCHAR_TYPE__ */
But "gcc-config -l" shows:
Code:
 [1] i686-pc-linux-gnu-3.3.6
 [2] i686-pc-linux-gnu-4.1.2 *
So what am I doing wrong?
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Mon Dec 03, 2007 4:19 pm    Post subject: Reply with quote

dirtyepic wrote:
well because unicode is the only option now, there's no USE flag. i'm not sure exactly what you're asking for.

I see. There is no problem then. Now that there is no unicode use flag, things become easier. I'll adjust the C::B ebuild. It is easy to fix.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Mon Dec 03, 2007 7:46 pm    Post subject: Reply with quote

New revision 18. Now, codeblocks-9999-r18 uses wxGTK-2.8.6.x that's in portage. Please remove the eclass and wxGTK that comes with previous cb ebuild revision 17. This is unicode only, since wxGTK-2.8.6.1 is unicode only. If you need ansi build, use rev 17 with use flag "-contrib" along with wxGTK-2.6.4.x. It should work, but not so sure. Because I don't know if C::B devs keep wxGTK-2.6.x compability.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"


Last edited by keenblade on Mon Dec 03, 2007 8:59 pm; edited 3 times in total
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Mon Dec 03, 2007 8:34 pm    Post subject: Reply with quote

Yamakuzure wrote:
Could unicode be the problem why c::b compiles well on one machin (has unicode support) and on the other it doesn't, where I do not have unicode support?

On the machine in question I can't use unicode, because I am using an ext2/3 partition to store data for use with linux and windows. The windows ext2 drivers unfortunately do not support unicode. :( I wouldn't fancy to "go back" to FAT32, but if I have to... well...

Yamakuzure, I think you maybe interested in AndLinux. It even runs almost all Linux applications without modification in your windows os. (though I have not used it)
Yamakuzure wrote:
... btw.:
... wxGTK 2.8 was the only version installed...

But I am compiling c::b right now with USE="-contrib" again...

Look at my previous post for ansi builds.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
spaetzle
n00b
n00b


Joined: 26 Aug 2003
Posts: 10

PostPosted: Mon Dec 03, 2007 9:47 pm    Post subject: compile error, affected ebuilds r17, r18 Reply with quote

There's wrong code in both ebuilds, r17 fails for me, r18 i havn't tried.

Code:
CB_REV=`LC_ALL=C svn info "${ESVN_CO_DIR}/trunk" | grep Revision: | cut -d" " -f2`;
CB_LCD=`LC_ALL=C svn info "${ESVN_CO_DIR}/trunk" | grep "^Last Changed Date:" | cut -d" " -f4,5`;

creates revision and date lookups in
Code:
distfiles/svn-src/codeblocks-9999/trunk/trunk/



This directory isn't under version control, that causes an compile error.
src/include/autorevision.h looks as follows:
Code:
/**/
#ifndef AUTOREVISION_H
#define AUTOREVISION_H

#include <wx/string.h>

namespace autorevision
{
        const unsigned int svn_revision = ;
        const wxString svnRevision(_T(""));
        const wxString svnDate(_T(""));
}
#endif


The ebuild code should be:
Code:
CB_REV=`LC_ALL=C svn info "${ESVN_CO_DIR}" | grep Revision: | cut -d" " -f2`;
CB_LCD=`LC_ALL=C svn info "${ESVN_CO_DIR}" | grep "^Last Changed Date:" | cut -d" " -f4,5`;


Bye
Christian
Back to top
View user's profile Send private message
rhill
Retired Dev
Retired Dev


Joined: 22 Oct 2004
Posts: 1629
Location: sk.ca

PostPosted: Mon Dec 03, 2007 10:41 pm    Post subject: Reply with quote

keenblade wrote:
dirtyepic wrote:
well because unicode is the only option now, there's no USE flag. i'm not sure exactly what you're asking for.

I see. There is no problem then. Now that there is no unicode use flag, things become easier. I'll adjust the C::B ebuild. It is easy to fix.


I'm glad to hear that. :o

I've updated wxGTK to 2.8.7.1. As soon as the arch teams finish keywording eselect-wxwidgets I'll be unmasking it.
_________________
by design, by neglect
for a fact or just for effect
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Tue Dec 04, 2007 12:02 am    Post subject: Re: compile error, affected ebuilds r17, r18 Reply with quote

spaetzle wrote:
There's wrong code in both ebuilds, r17 fails for me, r18 i havn't tried.

Code:
CB_REV=`LC_ALL=C svn info "${ESVN_CO_DIR}/trunk" | grep Revision: | cut -d" " -f2`;
CB_LCD=`LC_ALL=C svn info "${ESVN_CO_DIR}/trunk" | grep "^Last Changed Date:" | cut -d" " -f4,5`;

creates revision and date lookups in
Code:
distfiles/svn-src/codeblocks-9999/trunk/trunk/

...
Bye
Christian

What is your arch? In the ebuild:
Code:

echo "ESVN_CO_DIR : ${ESVN_CO_DIR}"

gives me:
Code:

ESVN_CO_DIR : /usr/portage/distfiles/svn-src/codeblocks-9999/

So there must be a bug in portage that needs "${ESVN_CO_DIR}/trunk" on ~amd64.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
spaetzle
n00b
n00b


Joined: 26 Aug 2003
Posts: 10

PostPosted: Tue Dec 04, 2007 1:25 am    Post subject: Reply with quote

arch is ~x86 for codeblocks

I've given r18 a try.
Code:
[snip]
>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-util/codeblocks-9999-r18/work/codeblocks-9999 ...
svn: '.' is not a working copy
svn: '.' is not a working copy
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
configure.in: installing `./install-sh'
configure.in: installing `./missing'
src/base/tinyxml/Makefile.am: installing `./depcomp'
/distfiles/svn-src/codeblocks-9999/trunk/trunk:  (Not a versioned resource)

/distfiles/svn-src/codeblocks-9999/trunk/trunk:  (Not a versioned resource)

 * Running eautoreconf in '/var/tmp/portage/dev-util/codeblocks-9999-r18/work/codeblocks-9999' ...
[snip]


I've no much knowledge about ebuild syntax, but
Code:
ESVN_CO_DIR="${PORTAGE_ACTUAL_DISTDIR-${DISTDIR}}"/svn-src/${P/-svn}/"${ESVN_REPO_URI##*/}"

looks for me like
Code:
distfiles/svn-src/<no idea what $P is but looks like 'codeblocks-9999'>/<looks like shellsyntax and so it must be 'trunk'>

and that's exactly what i can see on emerge output and what ebuild code stated:
Code:
CB_REV=`LC_ALL=C svn info "${ESVN_CO_DIR}/trunk" | grep Revision: | cut -d" " -f2`;

It expands to
Code:
CB_REV=`LC_ALL=C svn info "/distfiles/svn-src/codeblocks-9999/trunk/trunk" | grep Revision: | cut -d" " -f2`;


Result is a compile error:
Code:
../../src/include/autorevision.h:15: error: expected primary-expression before ';' token
make[3]: *** [configmanager-revision.lo] Error 1

because autorevision.h is created from template without valid CB_REV and CB_LCD values.
Assigning a default value '0' to CB_REV makes no sense because empty values will assigned to CB_REV and CB_LCD after that.

I'm a bit confused because you should get the same error.
Back to top
View user's profile Send private message
keenblade
Veteran
Veteran


Joined: 03 Oct 2004
Posts: 1087

PostPosted: Tue Dec 04, 2007 4:23 am    Post subject: Reply with quote

spaetzle wrote:
arch is ~x86 for codeblocks
...
Code:
CB_REV=`LC_ALL=C svn info "${ESVN_CO_DIR}/trunk" | grep Revision: | cut -d" " -f2`;

It expands to
Code:
CB_REV=`LC_ALL=C svn info "/distfiles/svn-src/codeblocks-9999/trunk/trunk" | grep Revision: | cut -d" " -f2`;


Result is a compile error:
Code:
../../src/include/autorevision.h:15: error: expected primary-expression before ';' token
make[3]: *** [configmanager-revision.lo] Error 1

because autorevision.h is created from template without valid CB_REV and CB_LCD values.
Assigning a default value '0' to CB_REV makes no sense because empty values will assigned to CB_REV and CB_LCD after that.

I'm a bit confused because you should get the same error.

I get that error, too, if I remove trunk and use "${ESVN_CO_DIR}" . That's confusing.
I use portage-2.1.4_rc4. What is your portage version? I'll try your version. If it behaves correctly than I will file a bug report for it.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1"
Back to top
View user's profile Send private message
spaetzle
n00b
n00b


Joined: 26 Aug 2003
Posts: 10

PostPosted: Tue Dec 04, 2007 8:09 am    Post subject: compile error, affected ebuilds r17, r18 Reply with quote

portage version is 2.1.3.19
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, 4, 5  Next
Page 3 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum