On 04/19/2010 01:55 PM, Charley Wang wrote:
Created a small section in the existing wiki page for now:
http://wiki.eclipse.org/Linux_Tools_Project/Valgrind/User_Guide#Other_Operating_Systems
Good luck with exams Elliott!
Thank you and great work Charley! I pulled your additions into the doc
* Charley Wang [2010-04-19 13:55]:
>
> - "Elliott Baron" wrote:
> > >
> > If you have the time that'd be great. Thanks a lot for trying it out
> > Charley!
>
> Created a small section in the existing wiki page for now:
>
> http://wiki.eclipse.org/Linux_Tools_Project/Valgrind/User_Guide#Oth
- "Elliott Baron" wrote:
> >
> If you have the time that'd be great. Thanks a lot for trying it out
> Charley!
Created a small section in the existing wiki page for now:
http://wiki.eclipse.org/Linux_Tools_Project/Valgrind/User_Guide#Other_Operating_Systems
Andrew -- should this informatio
On 04/15/2010 03:09 PM, Charley Wang wrote:
- "Elliott Baron" wrote:
I would be interested to see if a Mac OSX user has any difficulties
running the plugins. I don't see there being too many challenges,
considering it does provide a UNIX environment.
It works! It's a bit fiddly.
- "Elliott Baron" wrote:
> I would be interested to see if a Mac OSX user has any difficulties
> running the plugins. I don't see there being too many challenges,
> considering it does provide a UNIX environment.
It works! It's a bit fiddly. Have to apply some patches to the Valgrind
sour
- "Elliott Baron" wrote:
> On 04/14/2010 03:58 PM, Charley Wang wrote:
> > As a quick summary of supported OSes...
> >
> > Valgrind:
> > (various architectures)Linux, X86/Darwin (Mac OS X)
> >
> I would be interested to see if a Mac OSX user has any difficulties
> running the plugins. I
On 04/14/2010 03:58 PM, Charley Wang wrote:
As a quick summary of supported OSes...
Valgrind:
(various architectures)Linux, X86/Darwin (Mac OS X)
I would be interested to see if a Mac OSX user has any difficulties
running the plugins. I don't see there being too many challenges,
considerin
- "Andrew Overholt" wrote:
> I guess the question is whether or not tools like Valgrind exist on
> HP-UX. If we go with John's suggestion of not restricting to
> increase
> potential user base, and we know of the existence of underlying tools
> (ex. Valgrind, OProfile, SystemTap, LTTng) on s
> Is there a difference between "Linux" and "Unix" when we says "Linux Only" ?
The valid values for a feature's OS filter can be seen by clicking on
"Browse ..." next to the Operating System box in a feature.xml editor.
There's:
aix, hpux, linux, macosx, qnx, solaris, win32
I guess the question
Is there a difference between "Linux" and "Unix" when we says "Linux Only" ?
Because for what I see, most of our features would work on most
non-linux Unix (like Solaris) as well, since some others like LTTng
might not.
So for what I see there is like "Work on all Unixes with corect tools
install
* Charley Wang [2010-04-14 09:49]:
>
> - "Andrew Overholt" wrote:
>
> > * Jeff Johnston [2010-04-13 18:01]:
> > > IMO, the answer is to document it properly
> >
> > Please make sure this happens. I've opened a bug to track this:
> >
> > 309117: Document Autotools plugin usage on Windo
- "Andrew Overholt" wrote:
> * Jeff Johnston [2010-04-13 18:01]:
> > IMO, the answer is to document it properly
>
> Please make sure this happens. I've opened a bug to track this:
>
> 309117: Document Autotools plugin usage on Windows
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=3
- "Jeff Johnston" wrote:
>
> User expectations are not a problem if we document it as untested and
> officially unsupported on the other platforms. Our group is called
> "Linux Tools" and they have to type it in just to use the update site
> so
> it shouldn't be any surprise to a user that
* Anithra P Janakiraman [2010-04-14 01:59]:
> SystemTap is definitely Linux-only
I've made it so in SVN. Thanks.
Andrew
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
* John Arthorne [2010-04-14 09:26]:
> Just to chime in with an outside opinion, I think it's better to err on the
> side of allowing these features to be installed anywhere unless they really
> will only ever run on linux (i.e., non-optional dependency on bundles with
> Linux-specific native code)
* Xavier RAYNAUD [2010-04-14 04:29]:
> gprof and gcov are *not* linux only.
Okay.
> It's OK to use these plugins on windows - However, something like
> cygwin binutils must be in PATH.
It's issues like this we should _definitely_ ensure are documented.
I've opened these bugs to get GProf and GC
On 04/13/2010 04:39 PM, Andrew Overholt wrote:
> My concern is user expectations. If we just leave it in there for all
> OSes, people will assume it's been well-tested on all OSes. I'm
> inclined to restrict it to Linux-only for now and request testing on
> other operating systems. I'm willing t
* Jeff Johnston [2010-04-13 18:01]:
> IMO, the answer is to document it properly
Please make sure this happens. I've opened a bug to track this:
309117: Document Autotools plugin usage on Windows
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309117
Andrew
__
With Helios, one doesn't have to enter any update site and they will see
"Autotools support for CDT (Incubation)" under the "Programming
Languages" category.
I'm okay leaving autotools without an OS filter as I agree that
Cygwin/MinGW users will likely know issues involved. And if not, it's a
gre
Hi,
gprof and gcov are *not* linux only.
It's OK to use these plugins on windows - However, something like cygwin
binutils must be in PATH.
Xavier
Le 13/04/2010 21:20, Andrew Overholt a écrit :
Hi,
A few of our features will not function on non-Linux (or maybe non-Unix)
OSes. I'd like to e
On 04/14/2010 12:50 AM, Andrew Overholt wrote:
Hi,
Can the feature owners please tell me if their functionality will work
on non-Linux OSes? Since many of us are only testing on Linux, I'd
rather be conservative and ensure that the stuff we're shipping isn't
exposed to an audience who will only
On 04/13/2010 04:39 PM, Andrew Overholt wrote:
* Jeff Johnston [2010-04-13 16:29]:
Libhover and ChangeLog are OS-independent.
Okay, thanks.
Autotools is a bit trickier. It should work where there the
autotool and sh command exists (the Unix OSes plus Windows when
Cygwin or MingW is set up)
* Jeff Johnston [2010-04-13 16:29]:
> Libhover and ChangeLog are OS-independent.
Okay, thanks.
> Autotools is a bit trickier. It should work where there the
> autotool and sh command exists (the Unix OSes plus Windows when
> Cygwin or MingW is set up). Do we want to restrict it and wait for
>
On 04/13/2010 03:20 PM, Andrew Overholt wrote:
Hi,
A few of our features will not function on non-Linux (or maybe non-Unix)
OSes. I'd like to ensure that these features are not visible if one
views our update site from such an OS. I filed a bug to track this:
308661: Add OS filter to all f
24 matches
Mail list logo
