On Tue, Sep 23, 2014 at 9:09 PM, BAndViG <[email protected]> wrote: > Olof, I used FuseSoC once to download source code of modules from various > repositories and to generate tcl script for atlys board. After tcl was > generated the process stopped with error messages. Actually, it was normally > for my case as I didn't provide path for Xilinx tools into Cygwin > environment. As I found later it was right decision, because Xilinx's > Win-tools are compiled as native Win-programs, so they aren't able to work > with Unix stile paths anyway. So I edited the tcl: > (a) to replace paths from Unix to Win stile for both "xfile add" and > "Verilog Include Directories". > i.e. the initial part of a path like "/home..." was replaced by > "C:/cygwin64/home..." > (b) to remove any "process run" lines. > Next I used Xilinx ISE to open the tcl and ISE generated project. Since time > I have been using ISE only, not command line. > > Regarding other OR1K related tools. > > To build NewLIB tool chain I had to install 'autogen' package from > cygwinports.org (if somebody else interested, see http://cygwinports.org for > howto guide) because official Cygwin64 (!!) repositories don't include it. > > Other typical problems are symbolic links in repositories and file names > with symbols are forbidden for NTFS. Both problems are presented in uClibc. > Fortunately, the files with forbidden names are not used for or1k and the > only symbolic link was 'Config'. > The good guide on git simlinks in windows: > http://stackoverflow.com/questions/5917249/git-symlinks-in-windows . > > BR > Andrey > >
Good to know. Just using FuseSoC to get the sources and set up the inital project files was always one intended use case I see that there exists a cygpath command that automatically translates the paths to the proper windows paths. Using that when we detect that we're running under cygwin would be a nice improvement. Might make sense to remove the process run statements as well //Olof _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
