Well if Windows is not involved that is no issue. However with Windows in mind you have to notice that neither the format for mobile storage devices that can r/w out of the box on both Windows and UNIX systems which generally is FAT32, nor the Windows network share protocol which generally is SMB/CIFS supported that. That is, despite NTFS does both symbolic and hard links, I cannot easily transfer it from a UNIX system (I generally develop on OS X) to a Windows system.
发自我的 iPhone 在 2013-5-23，1:59，Niels Grewe <[email protected]> 写道： > > On 22.05.2013 18:47BST Chan Maxthon <[email protected]> wrote: > >> What I meant is not to use links but a common filesystem layout, as I may >> need to transfer the bundles through formats that does not accept symlinks. >> Binaries are compiled and linked separately, while the resources are shared, >> so library issue can be spotted and hunted architecture by architecture. > > *sigh* I give up. If you were willing or competent enough to check out the > non-flattened/multi-platform layout yourself, you would see that it does what > you describe (i.e. have architecture dependent stuff stored in properly > namespaces directories and architecture-independent resources shared). Since > you clearly are not, I don't see any use in trying to help you anymore. > > PS: Incidentally, there is no major platform that still comes with a > filesystem that does not support symbolic links. Even NTFS has that feature, > either as proper symlinks or as junction points. (mklink's the command) _______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
