Constant changes (Re-Build)

Hi I'm a student from Valencia-Venezuela and I'm working with some
other friends to make PostgreSQL allows the definition of Temporal
Databases and their respective Selection, Insertion and some other
functions needed to treat this paradigm (all based in TSQL2 Query
Language).

Right now we are working directly on the source code and making
different changes during the day, so I'd like to ask you which is the better
choice for re-building (I'm not sure if that is the right term) only the
code
files that I just have changed.

I'm working on a Slow PC with not to many recourse, so every time I
make (-configure/-make/-make-install/) i lose like 30 minutes of work,
and I have been thinking in some other way to only re-configure the files
I've recently changed.

Thanks anyway. I'll be waiting for your answer...

--
Luis D. García M.
Telf: 0414-3482018

- FACYT - UC -
- Computación -

luis garcia wrote:
> Hi I'm a student from Valencia-Venezuela and I'm working with some
> other friends to make PostgreSQL allows the definition of Temporal
> Databases and their respective Selection, Insertion and some other
> functions needed to treat this paradigm (all based in TSQL2 Query
> Language).
>
> Right now we are working directly on the source code and making
> different changes during the day, so I'd like to ask you which is the better
> choice for re-building (I'm not sure if that is the right term) only the
> code
> files that I just have changed.
>
> I'm working on a Slow PC with not to many recourse, so every time I
> make (-configure/-make/-make-install/) i lose like 30 minutes of work,
> and I have been thinking in some other way to only re-configure the files
> I've recently changed.

You don't need to configure each time. Just do a "make ; make install",
and that will only compile the files you changed. Be sure to use
the --enable-depend option to configure the first time, though.

You'd only need to mess with "configure" if you added directories, or
you changed configure input files (e.g. pg_config.h, configure.in, etc).

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

luis garcia wrote:
> Hi I'm a student from Valencia-Venezuela and I'm working with some
> other friends to make PostgreSQL allows the definition of Temporal
> Databases and their respective Selection, Insertion and some other
> functions needed to treat this paradigm (all based in TSQL2 Query
> Language).

That's interesting. May I suggest that you take a look at a book called
"Temporal Data & the Relational Model" by C.J. Date, Hugh Darwin and
Nikos Lorentzos
(http://www.amazon.com/Temporal-Relational-Kaufmann-Management-Systems/dp/1558608559).
It describes the best approach I've seen this far to dealing with
temporal data.

> Right now we are working directly on the source code and making
> different changes during the day, so I'd like to ask you which is the
> better
> choice for re-building (I'm not sure if that is the right term) only the
> code
> files that I just have changed.
>
> I'm working on a Slow PC with not to many recourse, so every time I
> make (-configure/-make/-make-install/) i lose like 30 minutes of work,
> and I have been thinking in some other way to only re-configure the files
> I've recently changed.

Well, you don't need to run configure every time you want to build. If
you just run "make", it will compile just the changes. I'd suggest
running the configure with the --enable-depend option, so it picks up
changes in header files better.

Also take a look at ccache (http://ccache.samba.org/). And if you have
more PCs to spare, you might want to set up distcc.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

Well Thanks you both for your answers, I really appreciate your opinions on
this subject.

And Heikki I would really like to take a look to that book. If I have the
chance to read it
I will tell you how the things go Ok...

Greets and Thanks one more time..

2006/9/27, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>:
>
> luis garcia wrote:
> > Hi I'm a student from Valencia-Venezuela and I'm working with some
> > other friends to make PostgreSQL allows the definition of Temporal
> > Databases and their respective Selection, Insertion and some other
> > functions needed to treat this paradigm (all based in TSQL2 Query
> > Language).
>
> That's interesting. May I suggest that you take a look at a book called
> "Temporal Data & the Relational Model" by C.J. Date, Hugh Darwin and
> Nikos Lorentzos
> (
> http://www.amazon.com/Temporal-Relational-Kaufmann-Management-Systems/dp/1558608559
> ).
> It describes the best approach I've seen this far to dealing with
> temporal data.
>
> > Right now we are working directly on the source code and making
> > different changes during the day, so I'd like to ask you which is the
> > better
> > choice for re-building (I'm not sure if that is the right term) only the
> > code
> > files that I just have changed.
> >
> > I'm working on a Slow PC with not to many recourse, so every time I
> > make (-configure/-make/-make-install/) i lose like 30 minutes of work,
> > and I have been thinking in some other way to only re-configure the
> files
> > I've recently changed.
>
> Well, you don't need to run configure every time you want to build. If
> you just run "make", it will compile just the changes. I'd suggest
> running the configure with the --enable-depend option, so it picks up
> changes in header files better.
>
> Also take a look at ccache (http://ccache.samba.org/). And if you have
> more PCs to spare, you might want to set up distcc.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
>

--
Luis D. García M.
Telf: 0414-3482018

- FACYT - UC -
- Computación -