search

fpjohnston / TECO-64

Enhanced and portable version of TECO text editor in C.
24 stars 6 forks source link

New target #9

Closed polluks closed 2 years ago

polluks commented 2 years ago

How about an "install" target for the makefile?

fpjohnston commented 2 years ago

I don't know how you've been using TECO or how you would like to use it; could you elaborate, so that I have a better idea what you're trying to accomplish? And is this just for you, or are there others who would benefit from such a feature?

On Thu, Apr 7, 2022 at 6:21 AM Stefan @.***> wrote:

How about an "install" target for the makefile?

— Reply to this email directly, view it on GitHub https://github.com/fpjohnston/TECO-64/issues/9, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK73X7AV7UBTJ7VZX6H5C7DVD2ZKXANCNFSM5SY4BQMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

polluks commented 2 years ago

An install target is pretty common like the clean one. For example install -s bin/teco /usr/local/bin

fpjohnston commented 2 years ago

I guess you're not going to answer my questions.

polluks commented 2 years ago

My motivation: Use this project without studying the implementation details. So the term common means I am not speaking for myself alone. By the way GNU also recommends make check for your make critic, see https://stackoverflow.com/questions/1735473/what-does-make-check-do.

fpjohnston commented 2 years ago

From the GNU documentation: make check is used to "set up any auxiliary programs or other files needed by the tests". But that's not the purpose of make critic, which I created to assist me in running .perlcritic on the Perl scripts I use during the build process. It should never be needed by an end user (which is why it's not displayed when executing the make help target. So I don't think that changing the name would make any sense. The documentation also says that it is typically used after running configure, something else I don't provide, along with the site.exp file that check commonly depends on.

I understood that you are not alone in expecting an install target for makefiles generally, but I was asking specifically about TECO. Are there multiple people you are aware of that are using it? And if so, can you tell me why any of you have chosen it over similar available tools? You said something some weeks ago about using it in an Amiga sandbox, but I'd like to know more.

fpjohnston commented 2 years ago

This issue has been closed due to lack of any further feedback.

fpjohnston commented 2 years ago

I posted a new release that includes an "install" target. This copies an executable image to /usr/local/bin, and also copies the lib/*.tec files to /usr/local/lib/teco.

fpjohnston commented 2 years ago

Latest version avoids the use of 'undefine' in makefiles.