Re: Compiling DLL's
FD(censored) wrote:
> I use a shared computer, and for organization purposes it is installed under
>
> "C:\program files\euphoria".
>
> I don't know if I am the only one who does this... but I instinctively
> dislike installing programs to a directory off C root.
>
> When trying to compile a DLL file recently I noticed in objfiles.lnk that
> quotation marks are excluded from the path of the
> "C:\Program Files\Euphoria\bin\ecwl.lib", resulting in the error: "cannot
> open c:\program". This is obviously fixed by editing the file and adding
> quotation marks, but surely it wouldn't hurt to add them as default as if
> the euphoria path *is* "C:\EUPHORIA" then it won't make any difference.
Hmm. Another problem with a path containing a blank.
I'll look into this. If it's easy to fix, I'll do it for 3.0.3,
otherwise I might wait until 3.0.4 to get into this.
There are probably numerous places to fix, and things still might
not work properly for all C compilers, linkers etc.
> I don't use linux, and only know marginally (strctly as much as I *have* to)
>
> about it for webservers. On one of my remote boxes when logged in I get this
>
> result when trying to arbitrarily compile any file:
>
> 3 .c files were created.
> To build your shared library, type: ./emake
> -jailshell-2.05b$ ./emake
> compiling with GNU C
> main-.c
> sort.c
> init-.c
> linking
> collect2: cannot find `ld'
>
> Can anyone help with this? I have *no* idea what linux flavour or anything
> its running, or how to find out.... it's just a standard"LAMP" setup.
When I type:
ld
at a command prompt, I get:
ld: no input files
which shows that ld (linker) is on my path.
When I type:
whereis ld
I get:
ld: /usr/bin/ld /usr/share/man/man1/ld.1.gz
So ld is in my /usr/bin directory. The other
reference must be the manual (documentation) page for ld.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
|
Not Categorized, Please Help
|
|
