From: Jose F. <j_r...@ya...> - 2002-02-26 17:35:07
|
Sorry for the duplicate (if there is any), I sent the previous with my university account by mistake. Here is the current directory structure of mingw-utils with all the program source unpacked on it as they were: . ./reimp ./reimp/bin ./reimp/src ./reimp/src/Makefile ./reimp/src/ar.c ./reimp/src/reimp.c ./reimp/src/reimp.h ./reimp/src/util.c ./reimp/README ./scripts ./scripts/dsw2mak.awk ./pexports ./pexports/bin ./pexports/COPYING ./pexports/pexports-0.41.diff ./pexports/README ./pexports/src ./pexports/src/ChangeLog ./pexports/src/hlex.c ./pexports/src/hlex.l ./pexports/src/hparse.c ./pexports/src/hparse.h ./pexports/src/hparse.y ./pexports/src/Makefile ./pexports/src/pe.h ./pexports/src/pexports.c ./pexports/src/pexports.h ./pexports/src/str_tree.c ./pexports/src/str_tree.h ./drmingw ./drmingw/bin ./drmingw/doc ./drmingw/doc/drmingw.html ./drmingw/doc/drmingw.reg ./drmingw/doc/exception-nt.gif ./drmingw/doc/install.gif ./drmingw/doc/sample.gif ./drmingw/samples ./drmingw/samples/exchndl2.cxx ./drmingw/samples/mingw ./drmingw/samples/mingw/test.exe ./drmingw/samples/mingw/test.RPT ./drmingw/samples/mingw.bat ./drmingw/samples/msvc ./drmingw/samples/msvc/test.exe ./drmingw/samples/msvc/test.pdb ./drmingw/samples/msvc/test.RPT ./drmingw/samples/msvc.bat ./drmingw/samples/test.cxx ./drmingw/samples/test2.c ./drmingw/samples/test2.exe ./drmingw/samples/test2.log ./drmingw/src ./drmingw/src/ansidecl.h ./drmingw/src/aout ./drmingw/src/aout/aout64.h ./drmingw/src/aout/stab.def ./drmingw/src/aout/stab_gnu.h ./drmingw/src/bfd.h ./drmingw/src/bfdlink.h ./drmingw/src/budbg.h ./drmingw/src/coff ./drmingw/src/coff/internal.h ./drmingw/src/cplus-dem.c ./drmingw/src/debug.c ./drmingw/src/debug.h ./drmingw/src/debugger.c ./drmingw/src/debugger.h ./drmingw/src/debugx.c ./drmingw/src/demangle.h ./drmingw/src/dialog.c ./drmingw/src/dialog.h ./drmingw/src/exchndl.c ./drmingw/src/getopt.h ./drmingw/src/icon.ico ./drmingw/src/ieee.c ./drmingw/src/ieee.h ./drmingw/src/include ./drmingw/src/include/ansidecl.h ./drmingw/src/include/bfd.h ./drmingw/src/include/bfdlink.h ./drmingw/src/include/demangle.h ./drmingw/src/include/dis-asm.h ./drmingw/src/include/getopt.h ./drmingw/src/include/libcoff.h ./drmingw/src/include/libiberty.h ./drmingw/src/log.c ./drmingw/src/log.h ./drmingw/src/main.c ./drmingw/src/Makefile ./drmingw/src/misc.c ./drmingw/src/misc.h ./drmingw/src/module.c ./drmingw/src/module.h ./drmingw/src/prdbg.c ./drmingw/src/psapi.def ./drmingw/src/rdcoff.c ./drmingw/src/rddbg.c ./drmingw/src/resource.h ./drmingw/src/resource.rc ./drmingw/src/stabs.c ./drmingw/src/symbols.c ./drmingw/src/symbols.h ./drmingw/src/tlHelp32.h ./drmingw/src/libbfd.a ./drmingw/src/libimagehlp.a ./drmingw/src/libpsapi.a ./redir ./redir/redir.c ./redir/README ./dos2unix ./dos2unix/COPYRIGHT ./dos2unix/dos2unix.1 ./dos2unix/dos2unix.c ./dos2unix/dos2unix.h ./dos2unix/dos2unix ./dos2unix/Makefile ./dos2unix/mac2unix ./dos2unix/INSTALL ./dos2unix/mac2unix.1 ./a2dll ./a2dll/a2dll ./a2dll/a2dll.html ./a2dll/COPYING ./a2dll/static2dll_howto.txt ./unix2dos ./unix2dos/unix2dos.1 ./unix2dos/unix2dos.c ./unix2dos/unix2dos.h ./unix2dos/COPYRIGHT My first question is if it's necessary to a `src` and `bin` and `doc` subdir in each one, or if all should be in just one? I think that the `bin` shouldn't be here because the binaries will be available by other means and wont be in CVS. I also think that the size of the programs doesn't justify to have a subdir for each one, but this is subjective of course. Either way the solution must be uniform to all, except perhaps the `scripts` directory. The second point is the libraries included in DrMingW source. They shouldn't be there. Some of them are import libs that I'll put in mingw-runtime if they aren't there already. libbfd.a could be distributed along with the mingw binutils release. tlHelp32.h was taken verbatim from the platform SDK and we must provide a cleanroom alternative instead. unix2dos and dos2unix were taken from a linux distribution and weren't yet ported. I don't know if there is a windows port already available that we could use instead. Regards, Jose' Fonseca |
From: Jose M. R. F. <me...@sw...> - 2002-02-26 17:28:03
|
Here is the current directory structure of mingw-utils with all the program source unpacked on it as they were: . ./reimp ./reimp/bin ./reimp/src ./reimp/src/Makefile ./reimp/src/ar.c ./reimp/src/reimp.c ./reimp/src/reimp.h ./reimp/src/util.c ./reimp/README ./scripts ./scripts/dsw2mak.awk ./pexports ./pexports/bin ./pexports/COPYING ./pexports/pexports-0.41.diff ./pexports/README ./pexports/src ./pexports/src/ChangeLog ./pexports/src/hlex.c ./pexports/src/hlex.l ./pexports/src/hparse.c ./pexports/src/hparse.h ./pexports/src/hparse.y ./pexports/src/Makefile ./pexports/src/pe.h ./pexports/src/pexports.c ./pexports/src/pexports.h ./pexports/src/str_tree.c ./pexports/src/str_tree.h ./drmingw ./drmingw/bin ./drmingw/doc ./drmingw/doc/drmingw.html ./drmingw/doc/drmingw.reg ./drmingw/doc/exception-nt.gif ./drmingw/doc/install.gif ./drmingw/doc/sample.gif ./drmingw/samples ./drmingw/samples/exchndl2.cxx ./drmingw/samples/mingw ./drmingw/samples/mingw/test.exe ./drmingw/samples/mingw/test.RPT ./drmingw/samples/mingw.bat ./drmingw/samples/msvc ./drmingw/samples/msvc/test.exe ./drmingw/samples/msvc/test.pdb ./drmingw/samples/msvc/test.RPT ./drmingw/samples/msvc.bat ./drmingw/samples/test.cxx ./drmingw/samples/test2.c ./drmingw/samples/test2.exe ./drmingw/samples/test2.log ./drmingw/src ./drmingw/src/ansidecl.h ./drmingw/src/aout ./drmingw/src/aout/aout64.h ./drmingw/src/aout/stab.def ./drmingw/src/aout/stab_gnu.h ./drmingw/src/bfd.h ./drmingw/src/bfdlink.h ./drmingw/src/budbg.h ./drmingw/src/coff ./drmingw/src/coff/internal.h ./drmingw/src/cplus-dem.c ./drmingw/src/debug.c ./drmingw/src/debug.h ./drmingw/src/debugger.c ./drmingw/src/debugger.h ./drmingw/src/debugx.c ./drmingw/src/demangle.h ./drmingw/src/dialog.c ./drmingw/src/dialog.h ./drmingw/src/exchndl.c ./drmingw/src/getopt.h ./drmingw/src/icon.ico ./drmingw/src/ieee.c ./drmingw/src/ieee.h ./drmingw/src/include ./drmingw/src/include/ansidecl.h ./drmingw/src/include/bfd.h ./drmingw/src/include/bfdlink.h ./drmingw/src/include/demangle.h ./drmingw/src/include/dis-asm.h ./drmingw/src/include/getopt.h ./drmingw/src/include/libcoff.h ./drmingw/src/include/libiberty.h ./drmingw/src/log.c ./drmingw/src/log.h ./drmingw/src/main.c ./drmingw/src/Makefile ./drmingw/src/misc.c ./drmingw/src/misc.h ./drmingw/src/module.c ./drmingw/src/module.h ./drmingw/src/prdbg.c ./drmingw/src/psapi.def ./drmingw/src/rdcoff.c ./drmingw/src/rddbg.c ./drmingw/src/resource.h ./drmingw/src/resource.rc ./drmingw/src/stabs.c ./drmingw/src/symbols.c ./drmingw/src/symbols.h ./drmingw/src/tlHelp32.h ./drmingw/src/libbfd.a ./drmingw/src/libimagehlp.a ./drmingw/src/libpsapi.a ./redir ./redir/redir.c ./redir/README ./dos2unix ./dos2unix/COPYRIGHT ./dos2unix/dos2unix.1 ./dos2unix/dos2unix.c ./dos2unix/dos2unix.h ./dos2unix/dos2unix ./dos2unix/Makefile ./dos2unix/mac2unix ./dos2unix/INSTALL ./dos2unix/mac2unix.1 ./a2dll ./a2dll/a2dll ./a2dll/a2dll.html ./a2dll/COPYING ./a2dll/static2dll_howto.txt ./unix2dos ./unix2dos/unix2dos.1 ./unix2dos/unix2dos.c ./unix2dos/unix2dos.h ./unix2dos/COPYRIGHT My first question is if it's necessary to a `src` and `bin` and `doc` subdir in each one, or if all should be in just one? I think that the `bin` shouldn't be here because the binaries will be available by other means and wont be in CVS. I also think that the size of the programs doesn't justify to have a subdir for each one, but this is subjective of course. Either way the solution must be uniform to all, except perhaps the `scripts` directory. The second point is the libraries included in DrMingW source. They shouldn't be there. Some of them are import libs that I'll put in mingw-runtime if they aren't there already. libbfd.a could be distributed along with the mingw binutils release. tlHelp32.h was taken verbatim from the platform SDK and we must provide a cleanroom alternative instead. unix2dos and dos2unix were taken from a linux distribution and weren't yet ported. I don't know if there is a windows port already available that we could use instead. Regards, Jose' Fonseca |
From: Earnie B. <ear...@ya...> - 2002-02-26 18:06:30
|
Jose Fonseca wrote: > > Sorry for the duplicate (if there is any), I sent the previous with my university account by mistake. > > Here is the current directory structure of mingw-utils with all the > program source unpacked on it as they were: > -8<- > > My first question is if it's necessary to a `src` and `bin` and `doc` > subdir in each one, or if all should be in just one? I think that the > `bin` shouldn't be here because the binaries will be available by other > means and wont be in CVS. I also think that the size of the programs > doesn't justify to have a subdir for each one, but this is subjective of > course. Either way the solution must be uniform to all, except perhaps > the `scripts` directory. > You're correct the bin directory shouldn't be included. No it's not necessary to have a src and doc directory in each package. You may want to autoconfisitcate your scripts in order to properly construct the shebang if nothing else. So for myscript I would have a file myscript.in that set the user chosen --prefix value during the configure/make process. If you choose to use myscript.in then they could just go to the src directory as well. > The second point is the libraries included in DrMingW source. They > shouldn't be there. Some of them are import libs that I'll put in > mingw-runtime if they aren't there already. libbfd.a could be > distributed along with the mingw binutils release. > I agree. > tlHelp32.h was taken verbatim from the platform SDK and we must provide > a cleanroom alternative instead. > One is already distributed via w32api. > unix2dos and dos2unix were taken from a linux distribution and weren't > yet ported. I don't know if there is a windows port already available > that we could use instead. > The old Mickey package had d2u and u2d. It shouldn't be that difficult to come up with our own version if we have to. I believe the UnixUtils site has these ported to Win32 and the code is in CVS. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Jose F. <j_r...@ya...> - 2002-02-26 18:16:01
|
On Tue, 2002-02-26 at 18:05, Earnie Boyd wrote: > .... > > You're correct the bin directory shouldn't be included. No it's not > necessary to have a src and doc directory in each package. You may want > to autoconfisitcate your scripts in order to properly construct the > shebang if nothing else. So for myscript I would have a file > myscript.in that set the user chosen --prefix value during the > configure/make process. If you choose to use myscript.in then they > could just go to the src directory as well. > I'm not familiar with the autotools, but is something that I planned to learn for a long time. I'll take this chance to do it then, putting the all mingw-utils autoconfigurable. > ... > > > unix2dos and dos2unix were taken from a linux distribution and weren't > > yet ported. I don't know if there is a windows port already available > > that we could use instead. > > > > The old Mickey package had d2u and u2d. It shouldn't be that difficult > to come up with our own version if we have to. I believe the UnixUtils > site has these ported to Win32 and the code is in CVS. > > Earnie. > I'll take a look on the source of both of these and choose. I would prefer that the binaries would be named dos2unix and unix2dos for consistence among Linux and cygwin (I think) as well. Regards, Jose Fonseca |
From: Earnie B. <ear...@ya...> - 2002-02-26 18:31:16
|
Jose Fonseca wrote: > > On Tue, 2002-02-26 at 18:05, Earnie Boyd wrote: > > .... > > > > You're correct the bin directory shouldn't be included. No it's not > > necessary to have a src and doc directory in each package. You may want > > to autoconfisitcate your scripts in order to properly construct the > > shebang if nothing else. So for myscript I would have a file > > myscript.in that set the user chosen --prefix value during the > > configure/make process. If you choose to use myscript.in then they > > could just go to the src directory as well. > > > > I'm not familiar with the autotools, but is something that I planned to > learn for a long time. I'll take this chance to do it then, putting the > all mingw-utils autoconfigurable. > Yes, please. The utils directory will be the top level directory where the configure.ac will go. Then each subpackage will have it's own Makefile.in and possibly it's own configure.ac but that isn't needed. I'm not that experienced with it either but the documentation is good. > > ... > > > > > unix2dos and dos2unix were taken from a linux distribution and weren't > > > yet ported. I don't know if there is a windows port already available > > > that we could use instead. > > > > > > > The old Mickey package had d2u and u2d. It shouldn't be that difficult > > to come up with our own version if we have to. I believe the UnixUtils > > site has these ported to Win32 and the code is in CVS. > > > > Earnie. > > > > I'll take a look on the source of both of these and choose. I would > prefer that the binaries would be named dos2unix and unix2dos for > consistence among Linux and cygwin (I think) as well. > It doesn't matter to me. A GUI wrapper might be nice as well. ;) Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |