[Eclipsedotnet-developers] RE: New Nant build files online

[<jpp...@gm...>]

I've been reviewing this and changed the build files to use the "normal"
resource naming routine (the default namespace + path from root to file =
+
file name thingie); since I named each build file's project as the =
default
namespace/plugin name and this project name can be accessed, this should
pose no problem. I also updated the resource-calling code (in the .cs =
files)
to reflect this naming.

The main reason for doing this was so that Nant was not the _only_ way =
to
correctly compile the platform; otherwise, assemblies built using VS =
would
not be able to access their own resources... This way, anyone who wants =
to
build using VS can do so (although they will have to copy auxilliary =
files
themselves...) and who wants to use Nant (probably everybody else :P ) =
can
also do it.

However, be advised. I still recommend the Nant way to build the =
platform
from scratch (because of the aux file copying thingie). If you plan to =
debug
using VS, I would recommend that you first build using Nant (so all =
files
are copied to their right places), and then build/debug using VS.


I don't remember anything else to say, so I'm off.

Regards,
JS


P.S.: To any subscribers of the eclipsedotnet-repositorycommits mailing
list: sorry for the huge load of mails yesterday :( .There were lots of =
new
directories created (because of the ToDeploy in each project dirs, and =
icon
dirs, and etc) and the cvs script automatically sends a mail when a
directory is created (this is useless in my opinion, but I don't know =
any
way to disable it), besides the mails that it sends when _real_ commits
occur. :( .

=20

> -----Original Message-----
> From: Jo=E3o Saraiva [mailto:jpp...@gm...]=20
> Sent: ter=E7a-feira, 20 de Dezembro de 2005 18:36
> To: 'ecl...@li...'
> Subject: New Nant build files online
>=20
> OK, this one is just to let you know that I _finally_ made=20
> the switch from building the Platform with VS to building=20
> with NAnt. The build files are available in the CVS=20
> repository, and there is 1 build file for each project and=20
> solution (and for the platform itself).
>=20
>=20
> For each project, I made available the targets "build" (just=20
> builds the dll and places it in the right place), "clean"=20
> (cleans the generated dlls and pdbs), "copyFiles" (copies=20
> auxilliary files, like plugin manifests, to the right place)=20
> and "deploy" (just calls "build" and "copyFiles). "build" and=20
> "copyFiles" are available only to projects (like Java or=20
> Core.Runtime).
>=20
> To build a project/plugin (like, say, Java or UI.WorkBench),=20
> go to the directory of the project and type: "nant deploy"=20
> (or "nant build"; see above for explanation).
>=20
> To build the set of Core plugins (or the SWT_UI plugins, or=20
> whatever), go to the directory where the respective solution=20
> resides and type (what else?): "nant deploy".
>=20
> To build the platform itself, go to the src_platform=20
> directory and type "nant deploy" .
>=20
>=20
> Also, I'm including in the src_platform module the libraries=20
> and other files needed to execute the platform, so that if=20
> the "bin" module has not been downloaded, "nant deploy" will=20
> indeed build everything, setting up the platform for first=20
> time use. This will also render the "bin" module obsolete=20
> (but I will not delete anything from it unless we all agree=20
> that the module is no longer needed; if anyone disagrees with=20
> this, you should let me know).
>=20
> I also took the opportunity to relocate some of the resource=20
> files, as VS has a nasty way to generate namespaces for=20
> embedded resources (I know that it should be <default=20
> namespace> + "." + <path from root of project to resource> +=20
> <name of resource> , but I've seen this rule not being=20
> applied sometimes... :\ ) So, with the new build files, the=20
> namespace should be nothing (unless otherwise specified in=20
> the build file, but I've left all resources at the empty namespace).
>=20
>=20
> Hopefully this will make it much easier to build the=20
> platform, and (finally) remove the dependency on VS that I=20
> had wanted to remove for so long a time...
>=20
> OK, nothing else coming to mind right now, so I'll end this mail here.
>=20
>=20
> If anyone has any comments, you know the address of the=20
> mailing list ;) .
>=20
>=20
> Best regards,
> JS
>=20
> P.S.: I'm still committing some of the files, so don't be=20
> surprised if some of the files don't appear right away.
>=20
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.1/207 - Release=20
> Date: 19-12-2005
> =20
>=20

--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.2/208 - Release Date: =
20-12-2005
=20