Date: Fri, 18 Jan 2019 00:35:21 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Method to properly recompile a port after tweaking Message-ID: <2bda16b8-da96-ba96-3ab4-c3e0f3ee13ba@FreeBSD.org> In-Reply-To: <16592fa8-d560-39ff-809b-2c19e05b7891@slac.stanford.edu> References: <16592fa8-d560-39ff-809b-2c19e05b7891@slac.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --AkTXO15BkcDqZyZZ4XpdWVTparbOBUASD Content-Type: multipart/mixed; boundary="cuKntJZMCyg5yML1mZaItotmwyXdSdMjI"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <2bda16b8-da96-ba96-3ab4-c3e0f3ee13ba@FreeBSD.org> Subject: Re: Method to properly recompile a port after tweaking References: <16592fa8-d560-39ff-809b-2c19e05b7891@slac.stanford.edu> In-Reply-To: <16592fa8-d560-39ff-809b-2c19e05b7891@slac.stanford.edu> --cuKntJZMCyg5yML1mZaItotmwyXdSdMjI Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 17/01/2019 19:38, Nicola Mingotti via freebsd-questions wrote: > I have recently modified the port editors/texmacs and found a way > to easily recompile it after each C++ code modification. >=20 > The method I used is basically: > #> rm work/.build_done.texmacs._usr_local > #> make build >=20 > When I was looking for the solution I opened a discussion > thread on the FreeBSD Forum: > https://forums.freebsd.org/threads/how-to-tweak-the-source-of-an-existi= ng-port.69164/#post-413736 >=20 >=20 > The problem is that a user says the method to him is not working. >=20 > Could you please tell me what is the official way to recompile a port? > I am aware of > #> maker clean > #> make build > but that way too slow, it recompiles all, even if nor necessary. Ports aren't really set up for incremental development the way you are doing. For normal use they're compiled one time into a package and then installed. Where you need to modify the port, generally you'ld get into a cycle of compile, modify, clean, re-compile from scratch, rinse, repeat ... For the vast majority of ports, the compilation step takes only a few minutes on reasonable hardware so this isn't really a huge burden. Bigger and more complex programs will need an iterative approach as you are doing to develop local patches and then a final clean and complete build. You can often just run make from within the $WRKDIR of the port to incrementally rebuild after code changes, or you can remove the =2Ebuild_done file and rerun the build target of the port. Cheers, Matthew --cuKntJZMCyg5yML1mZaItotmwyXdSdMjI-- --AkTXO15BkcDqZyZZ4XpdWVTparbOBUASD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlxBH0pfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDE5 RjE1NEVDQkYxMTJFNTA1NDRFM0YzMDAwNTEzRjEwRTBBOUU0RTcACgkQAFE/EOCp 5Offlg/+I3mRhdTp27v8UNZx4oY+rVSioL36+XvlA7OQe6CmfNazQzofEGyD5Mds lHr9d7rCuzPvpdVyfTZCy1hRCvPZR0YCh3R1GfUFCVjR1DoiEPDL9x5k5eqhzkIS rudcHPy8oMPFNY2dvnh4ijZHBt19ayKGYpH7njD8myrgc24F/MLV8Ejd6NWr74WL 2ZxkhVjv50NqdiCygBpSJo9i98jzR91qsCfyI4jS7AZDfU5TJ4uHeLQDSRNO8DfO U4gLfFpOvQ9nARSB5xrFqz4RI6o0zJx8PeUSJ8DLOy+yefS/J4b+TVQRXyz9+Sde BawusRfHzO8S6B4IFBP2jWYjoXxmm1FP6zS4Ai2F0UkR18dta40IhnzGWP5ukpCx M54HULc7QLoeUj0tFuEwpzffDYenvnuUf6vN273m+yLLQl8VrgarBEQvwx+YN9i6 IcAZJphBwYvELhkik63qRT/OhXK42OZZtluNPmaqd6bdldN3D1qXASkVyg4DG0x1 eD0AwWapqoLajvZvc11ibJb/2Aj+caF0xtYiMaRBfYv97J7BQGtvPSPubXUjll1+ PMJ6GIGAWtwCaphx3Q2aTgAVQPFOeAbO/QwGuCnBtOU3GvCcIPHHtzPZZUJe/nvd x63InJtc67qla3484TMb/HgKEEJADcwYzre+CLC3YB5V5jO+ZgE= =4wYJ -----END PGP SIGNATURE----- --AkTXO15BkcDqZyZZ4XpdWVTparbOBUASD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2bda16b8-da96-ba96-3ab4-c3e0f3ee13ba>