gnupic: Re: [gnupic] relocatable code libraries and pikdev


Previous by date: 27 Dec 2005 22:33:46 +0000 Re: [gnupic] relocatable code libraries, Greg Hill
Next by date: 27 Dec 2005 22:33:46 +0000 pikdev & gpsim interoperability, John De Villiers
Previous in thread:
Next in thread:

Subject: Re: [gnupic] relocatable code libraries and pikdev
From: John De Villiers ####@####.####
Date: 27 Dec 2005 22:33:46 +0000
Message-Id: <1135722786.4886.50.camel@bbj.inet>

Ok its late, and im replying to myself so all is not right.

What i did find though is that i can add the .asm of my code library to
the project and then pikdev will compile it. It still places the .o file
in the same folder as the .asm, where i would've prefered it in the
folder where the project is. That way my library folder will always only
contain the .asm folders.

Alain, would you consider a feature like that for the future ? Also a
button to launch gpsim from pikdev ?

On Wed, 2005-12-28 at 00:09, John De Villiers wrote:
> ...time passes...
> dagnabbit
> I cant compile a relocatable object without specifying the processor
> type ( which makes sense ).

> Is there a way to make pikdev use Makefiles to grab the .asm out of the
> lib, but place the .o file in the project folder ? 
> 



Previous by date: 27 Dec 2005 22:33:46 +0000 Re: [gnupic] relocatable code libraries, Greg Hill
Next by date: 27 Dec 2005 22:33:46 +0000 pikdev & gpsim interoperability, John De Villiers
Previous in thread:
Next in thread:


Powered by ezmlm-browse 0.20.