Browsing this Thread:
1 Anonymous Users
|
Re: Murks/GCC Compiling Issues on SFS Volumes?
|
||||
|---|---|---|---|---|
|
Not too shy to talk
 
|
Not a problem. I just moved all of my sources and projects to an FFS volume and everything seems to work fine now.
I'll take a peek at the source at some point. Thanks for the reply.
Posted on: 2007/11/28 16:38
|
|||
|
When swimming with sharks, make sure to bring band-aids...
|
||||
|
||||
|
Re: Murks/GCC Compiling Issues on SFS Volumes?
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
Quote:
mmhhh I never tried it with SFS. To your question, no Murks does not have the option to create the output file in a different directory yet. I dont have much time in the next two month, so I will probably not add this funtionality until next year. But as Murks is OpenSource, feel free to add this by yourself. All you need is Murks Source and AmiDevCpp If you make it work, please eternalize yourself in the Source Code and upload it to aros-archives.
Posted on: 2007/11/28 10:06
|
|||
|
||||
|
Re: Murks/GCC Compiling Issues on SFS Volumes?
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Try upgrading to the latest version as you pointed out yesterday. Download it directly in AROS with AAEDT if possible, or with any browser in the host operating system, then ftp it to PUB:. Since then, you can unpack it to the work:development drawer with the proper unarchiver. Unluckily SFS has some compatibility issues, however when I put MurdksIDE on VmwAROS I tried compiling the example script and they worked flawlessly.
Posted on: 2007/11/28 9:11
|
|||
|
p.bes
Icaros Desktop AROS distribution mantainer |
||||
|
||||
|
Murks/GCC Compiling Issues on SFS Volumes?
|
||||
|---|---|---|---|---|
|
Not too shy to talk
|
Maybe it's just me, or perhaps this is even known already, but I noticed that Murks (but this is really a GCC issue) has issues in trying to create object files when compiling projects on the Works/DH1: volume, but not the AROS/DH0: or RAM: volumes. Could it be something to do with the fact that Works is formatted SFS (Smart File System)? If I use gcc directly, I have same problem unless I specify that the object file should be on another volume (e.g. -o RAM:filename.o).
In any case, this is annoying because when MurksIDE spawns GCC during a build , it specifies the path of object file to be the same as that of the main source main and this is not configurable in Murks...at least not to my knowledge. Any ideas as to what I should do, other than of course ensuring that I put all of my projects and source files on a non-SFS volume when working through Murks? I thought the whole point of using SFS is that it is less prone to corruption, so I would prefer to have my work on an SFS drive it at all possible.
Posted on: 2007/11/27 22:37
|
|||
|
When swimming with sharks, make sure to bring band-aids...
|
||||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
