Hi,
I would like it if I can build ros outside from the source tree. This makes it possible to build ros with different configurations from the same (highly modified) source tree.
- Hartmut
I would like it if I can build ros outside from the source tree. This makes it possible to build ros with different configurations from the same (highly modified) source tree.
You can use the export fucntion in your svn client and export the "trunk\reactos" directory.
Klemens Friedl
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Hartmut Birr Sent: 28. marts 2005 11:09 To: ReactOS Development List Subject: [ros-dev] feature request for (xml) build
Hi,
I would like it if I can build ros outside from the source tree. This makes it possible to build ros with different configurations from the same (highly modified) source tree.
- Hartmut
This is already implemented, but make is giving us a lot of trouble. The semantics of the last modified time on non-FAT volumes (eg. NTFS and EXT2) is to be updated once an entry within the directory is created or changed. We have generated files depend on their parent directories so we can make sure the parent directories exist before putting files in them. This, unfortunately, causes spurious rebuilding of targets and even looping during build. I have patched make to always use the creation time instead of the last modified time for directories. This works, but it will unfortunately require a custom make unless we can find another solution.
Casper
On Mon, 28 Mar 2005 13:01:34 +0200 "Casper Hornstrup" ch@csh-consult.dk wrote:
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Hartmut Birr Sent: 28. marts 2005 11:09 To: ReactOS Development List Subject: [ros-dev] feature request for (xml) build
Hi,
I would like it if I can build ros outside from the source tree. This makes it possible to build ros with different configurations from the same (highly modified) source tree.
- Hartmut
This is already implemented, but make is giving us a lot of trouble. The semantics of the last modified time on non-FAT volumes (eg. NTFS and EXT2) is to be updated once an entry within the directory is created or changed. We have generated files depend on their parent directories so we can make sure the parent directories exist before putting files in them. This, unfortunately, causes spurious rebuilding of targets and even looping during build. I have patched make to always use the creation time instead of the last modified time for directories. This works, but it will unfortunately require a custom make unless we can find another solution.
In my old bootstrap makefile I used a special target to make all directories first. I think it's a reasonable solution.
-----Original Message----- From: art yerkes [mailto:ayerkes@speakeasy.net] Sent: 28. marts 2005 14:07 To: ReactOS Development List Cc: ch@csh-consult.dk Subject: Re: [ros-dev] feature request for (xml) build
On Mon, 28 Mar 2005 13:01:34 +0200 "Casper Hornstrup" ch@csh-consult.dk wrote:
This is already implemented, but make is giving us a lot of trouble. The semantics of the last modified time on non-FAT volumes (eg. NTFS and EXT2) is to be updated once an entry within the directory is created or changed. We have generated files depend on their parent directories so we can make sure the parent directories exist before putting files in them. This, unfortunately, causes spurious rebuilding of targets and even looping during build. I have patched make to always use the creation time instead of the last modified time for directories. This works, but it will unfortunately require a custom make unless we can find another solution.
In my old bootstrap makefile I used a special target to make all directories first. I think it's a reasonable solution.
I don't like the consequence that you need to remember to do a "make directories" before a "make" after each "svn up". That doubles the number of steps to do after an update.
Casper
-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Casper Hornstrup Sent: 28. marts 2005 13:41 To: 'ReactOS Development List' Subject: RE: [ros-dev] feature request for (xml) build
-----Original Message----- From: art yerkes [mailto:ayerkes@speakeasy.net] Sent: 28. marts 2005 14:07 To: ReactOS Development List Cc: ch@csh-consult.dk Subject: Re: [ros-dev] feature request for (xml) build
On Mon, 28 Mar 2005 13:01:34 +0200 "Casper Hornstrup" ch@csh-consult.dk wrote:
This is already implemented, but make is giving us a lot of trouble. The semantics of the last modified time on non-FAT volumes (eg. NTFS and EXT2) is to be updated once an entry within the directory is created or changed. We have generated files depend on their parent directories so we can make sure the parent directories exist before putting files in them. This, unfortunately, causes spurious rebuilding of targets and even looping during build. I have patched make to always use the creation time instead of the last modified time for directories. This works, but it will unfortunately require a custom make unless we can find another solution.
In my old bootstrap makefile I used a special target to make all directories first. I think it's a reasonable solution.
I don't like the consequence that you need to remember to do a "make directories" before a "make" after each "svn up". That doubles the number of steps to do after an update.
Casper
Actually, rbuild currently generates some files in the source directory. I'd like for it to generate them in the intermediate output tree instead. To do that, rbuild needs to create the directories, not make. This will mean that you would have to pass the ROS_INTERMEDIATE and ROS_OUTPUT variables to rbuild instead of make. A consequence of this is that you need to run rbuild to change ROS_INTERMEDIATE and ROS_OUTPUT locations, but this is not a big problem IMHO.
Casper
-
art yerkes -
Casper Hornstrup -
Hartmut Birr -
Klemens Friedl