Xilinx should try whatever Altera uses.
Their Linux version of their tools seems to work fine.

Wilbur

Alex Gibson wrote:

>"Rudolf Usselmann" <russelmann@hotmail.com> wrote in message 
>news:cgpi22$lkk$1@nobel.pacific.net.sg...
>  
>
>>Stephen Williams wrote:
>>
>>    
>>
>>>Brad Smallridge wrote:
>>>      
>>>
>>>>Maybe it's one of those spaces in the path names problems disguised as
>>>>path too long.
>>>>        
>>>>
>>>Might be.
>>>
>>>Have I mentioned yet that I hate this Wind/U atrocity?-)
>>>
>>>      
>>>
>>I have to jump in here !
>>
>>This Wind/U crap is made by some sort of a third party, to
>>"easy" "porting" of windows applications to unix like systems.
>>
>>I can't see the usability of any GIUs made with this Wind/U
>>stuff. Did anybody try to use EDK on Linux ? C'mon, I am
>>trying to get a job done not finding out alternative ways
>>to use a mouse and a keyboard.
>>
>>Great to see the results from the Wind/U "porting" tools.
>>Don't have to bother evaluating or trying it out for any
>>of our projects - what a piece of crap !!!
>>
>>If Xilinx could find an alternative to this Wind/U, I think
>>they would have an excellent tool flow for Linux (plus fixing
>>the paralle port support to something native of course).
>>
>>    
>>
>
>Well if they ever need a cross platform gui
>they should look at wxwidget (was wxwindows )
>http://www.wxwindows.org/
>available for windows , linux and mac ox
>as well as support for x,  gtk+ , motif
>
>for some screenshots follow the links
>http://www.wxwindows.org/screensh.htm
>
>for a list of users which includes AMD , AOL , Green Mountain(VHDL Studio), 
>ING (Bank),
>Lockheed Martin, Ecos, Scitech , Xerox and others
>http://www.wxwindows.org/users.htm
>
>for a list of applications writen using it
>http://www.wxwindows.org/apps.htm
>
>wxperl  http://wxperl.sourceforge.net/
>wxpython http://wxpython.org
>are bindings for those languages
>
>Probably take a bit / while to rewrite  but to have one
>common main project  would make it easier to
>support multiple platforms.
>
>
>Alex 
>
>
>  
>

Rudolf Usselmann wrote:
> ...
> If Xilinx could find an alternative to this Wind/U, I think
> they would have an excellent tool flow for Linux (plus fixing
> the paralle port support to something native of course).
> 

Apparently, Xilinx is doing just that, as mentioned a few days ago in 
another thread. Scroll down to message 5 in the thread.
http://tinyurl.com/636ab

-- 
My real email is akamail.com@dclark (or something like that).

"Rudolf Usselmann" <russelmann@hotmail.com> wrote in message 
news:cgpi22$lkk$1@nobel.pacific.net.sg...
> Stephen Williams wrote:
>
>> Brad Smallridge wrote:
>>> Maybe it's one of those spaces in the path names problems disguised as
>>> path too long.
>>
>> Might be.
>>
>> Have I mentioned yet that I hate this Wind/U atrocity?-)
>>
>
> I have to jump in here !
>
> This Wind/U crap is made by some sort of a third party, to
> "easy" "porting" of windows applications to unix like systems.
>
> I can't see the usability of any GIUs made with this Wind/U
> stuff. Did anybody try to use EDK on Linux ? C'mon, I am
> trying to get a job done not finding out alternative ways
> to use a mouse and a keyboard.
>
> Great to see the results from the Wind/U "porting" tools.
> Don't have to bother evaluating or trying it out for any
> of our projects - what a piece of crap !!!
>
> If Xilinx could find an alternative to this Wind/U, I think
> they would have an excellent tool flow for Linux (plus fixing
> the paralle port support to something native of course).
>

Well if they ever need a cross platform gui
they should look at wxwidget (was wxwindows )
http://www.wxwindows.org/
available for windows , linux and mac ox
as well as support for x,  gtk+ , motif

for some screenshots follow the links
http://www.wxwindows.org/screensh.htm

for a list of users which includes AMD , AOL , Green Mountain(VHDL Studio), 
ING (Bank),
Lockheed Martin, Ecos, Scitech , Xerox and others
http://www.wxwindows.org/users.htm

for a list of applications writen using it
http://www.wxwindows.org/apps.htm

wxperl  http://wxperl.sourceforge.net/
wxpython http://wxpython.org
are bindings for those languages

Probably take a bit / while to rewrite  but to have one
common main project  would make it easier to
support multiple platforms.


Alex 

Stephen Williams wrote:

> Brad Smallridge wrote:
>> Maybe it's one of those spaces in the path names problems disguised as
>> path too long.
> 
> Might be.
> 
> I found that there was a ~/.windu.flask directory as well as a
> .WindU file that needed deleting. Deleted the directory and I am
> back to life. *Whew*!
> 
> I did notice that the various dialogue boxes get very confused
> and start storing garbage if you type control chracters or arrow
> keys in the various text entry fields. It is possible that just
> the right bit of junk got into its brain that it finally went
> insane.
> 
> Have I mentioned yet that I hate this Wind/U atrocity?-)
>

I have to jump in here !

This Wind/U crap is made by some sort of a third party, to
"easy" "porting" of windows applications to unix like systems.

I can't see the usability of any GIUs made with this Wind/U
stuff. Did anybody try to use EDK on Linux ? C'mon, I am
trying to get a job done not finding out alternative ways
to use a mouse and a keyboard.

Great to see the results from the Wind/U "porting" tools. 
Don't have to bother evaluating or trying it out for any
of our projects - what a piece of crap !!!

If Xilinx could find an alternative to this Wind/U, I think
they would have an excellent tool flow for Linux (plus fixing
the paralle port support to something native of course).

Regards,
rudi               
=============================================================
Rudolf Usselmann,  ASICS World Services,  http://www.asics.ws
Your Partner for IP Cores, Design, Verification and Synthesis



> Anyhow, I now get to deal with the consequences of accidently
> pushing Vref of a PC-IV pod on to GND. You would think that a
> $100 device would make a bigger spark:-/
> 

Neil Glenn Jacobson wrote:
> So, *when* do you get this message?  When you are generating an ACE 
> file?  When you are accessing the cable?  When you are trying to write 
> the ACE files to the compact flash? Spotaneously for no apparent reason? 
> What were you doing when it started to appear?

Any time it is about to ask the user for a file. For example, when
I select (at startup) that I want to open an existing cdf file, it
instead of asking me to browse for the file put up a little dialog
box that said:

   Can't access this folder
   Path is too long

But like I said elsewhere in the thread, it appears there was some
sort of poison in the ~/.windu.hostname directory. Removing that
directory got me out of the problem. It may be (blind speculation)
that the file got corrupted somehow, so that the initial directory
where file selection boxes go was an invalid directory.

> [The .WindU file is important and will always be regenerated so don't 
> mess with it]

So far as I can tell, there are only 2 things that can be safely
done with the file: ignore it or remove it. Generally, ignoring it
is the best plan, but this time I was left with the other option.

> 
> Stephen Williams wrote:
> 
>>
>> I filed a WebCase over this, but I'm going to ask here in case
>> others have run into this problem as well. I expect the Linux
>> User Density to be higher here then at Xilinx Support:-)
>>
>> I have impact from ISE 6.2i installed on a Linux/Intel machine,
>> so that I can use the PC-IV cable. It was working for a while,
>> but now all the sudden it ishopelessly non-functional. All I
>> get is I dialog box with the message:
>>
>>  Can't access this folder
>>  Path is too long
>>
>> I don't know if this matters, but I've been running impact on my
>> main workstation for a while, making ACE files for another project
>> (open source, stay tuned) and that has been and still does work
>> fine. My home directory is shared. I've tried removing the .WindU
>> file that keeps appearing.
>>
>> (For the record, I find this Wind/U thing phenomenally klunky
>> and embarassingly slow.)
>>
> 


-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

So, *when* do you get this message?  When you are generating an ACE 
file?  When you are accessing the cable?  When you are trying to write 
the ACE files to the compact flash? Spotaneously for no apparent reason? 
 What were you doing when it started to appear?

[The .WindU file is important and will always be regenerated so don't 
mess with it]


Stephen Williams wrote:

>
> I filed a WebCase over this, but I'm going to ask here in case
> others have run into this problem as well. I expect the Linux
> User Density to be higher here then at Xilinx Support:-)
>
> I have impact from ISE 6.2i installed on a Linux/Intel machine,
> so that I can use the PC-IV cable. It was working for a while,
> but now all the sudden it ishopelessly non-functional. All I
> get is I dialog box with the message:
>
>  Can't access this folder
>  Path is too long
>
> I don't know if this matters, but I've been running impact on my
> main workstation for a while, making ACE files for another project
> (open source, stay tuned) and that has been and still does work
> fine. My home directory is shared. I've tried removing the .WindU
> file that keeps appearing.
>
> (For the record, I find this Wind/U thing phenomenally klunky
> and embarassingly slow.)
>

Brad Smallridge wrote:
> Maybe it's one of those spaces in the path names problems disguised as path
> too long.

Might be.

I found that there was a ~/.windu.flask directory as well as a
.WindU file that needed deleting. Deleted the directory and I am
back to life. *Whew*!

I did notice that the various dialogue boxes get very confused
and start storing garbage if you type control chracters or arrow
keys in the various text entry fields. It is possible that just
the right bit of junk got into its brain that it finally went
insane.

Have I mentioned yet that I hate this Wind/U atrocity?-)

Anyhow, I now get to deal with the consequences of accidently
pushing Vref of a PC-IV pod on to GND. You would think that a
$100 device would make a bigger spark:-/

-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Maybe it's one of those spaces in the path names problems disguised as path
too long.

I filed a WebCase over this, but I'm going to ask here in case
others have run into this problem as well. I expect the Linux
User Density to be higher here then at Xilinx Support:-)

I have impact from ISE 6.2i installed on a Linux/Intel machine,
so that I can use the PC-IV cable. It was working for a while,
but now all the sudden it ishopelessly non-functional. All I
get is I dialog box with the message:

  Can't access this folder
  Path is too long

I don't know if this matters, but I've been running impact on my
main workstation for a while, making ACE files for another project
(open source, stay tuned) and that has been and still does work
fine. My home directory is shared. I've tried removing the .WindU
file that keeps appearing.

(For the record, I find this Wind/U thing phenomenally klunky
and embarassingly slow.)

-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."