Which source file contains the lexer (scanner) for make file?
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Implementation of what?
I sent you the source of make, you can browse the whole repo to find anything you are interested in.
So, all the functionality specified by the manual, as specified by @NevemTeve, is implemented in that source file of make?
Do you mean that the other files here, are not needed for the given purpose?
If yes, still it is an uphill task for me.
When you have finished a basic C-programming course, you will be able to understand (parts of) the source of gmake. Of course the source is completely irrelevant, as you only only want to use gmake.
So, all the functionality specified by the manual, as specified by @NevemTeve, is implemented in that source file of make?
Do you mean that the other files here, are not needed for the given purpose?
If yes, still it is an uphill task for me.
I still don't understand. Yes, those are the source files of make, if you want to know how it is implemented. But that is not required at all, if you want to use this tool. In that case you need to learn to use it, so read the manual and tutorials and examples, but do not read the source code.
Understanding the full source code is not not an easy task at all, not only for you, but for almost everybody.
I still don't understand. Yes, those are the source files of make, if you want to know how it is implemented. But that is not required at all, if you want to use this tool. In that case you need to learn to use it, so read the manual and tutorials and examples, but do not read the source code.
Understanding the full source code is not not an easy task at all, not only for you, but for almost everybody.
Thanks, but my interest is still there in getting the ability to be able to comprehend the source code, though as a side activity to understanding the use of makefile.
In fact, it is a very good exercise, for any student too.
Hence, request to please answer to my last post, i.e. if the given code file, is having all the functionality of makefiles, in it; or there are more files that implement any of the functionality of the makefiles.
Thanks, but my interest is still there in getting the ability to be able to comprehend the source code, though as a side activity to understanding the use of makefile.
In fact, it is a very good exercise, for any student too.
Hence, request to please answer to my last post, i.e. if the given code file, is having all the functionality of makefiles, in it; or there are more files that implement any of the functionality of the makefiles.
Assuming your question is actually...
Quote:
my last post ...if the given code file, is having all the functionality of make, in it; or there are more files that implement any of the functionality of the make.
Have you not looked at the source tree for make? In particular follow the src/ directory. All of those files are obviously needed in some way to build the make application.
Have you not looked at the source tree for make? In particular follow the src/ directory. All of those files are obviously needed in some way to build the make application.
I asked that question, as @pan64 stated earlier (in post #29), in an implicit manner, that all of the functionality of the makefile lies in the given code file. So, wanted to confirm that more clearly; as it seems that the rest of the files are important, but peripheral.
all of the functionalities are there, but not in one file. All the files (especially inside src) are parts of the implementation.
Again, understanding the c code and using make are two different things.
all of the functionalities are there, but not in one file. All the files (especially inside src) are parts of the implementation.
Again, understanding the c code and using make are two different things.
Very difficult unless some pointer is made to a specific functionality, say the code fragment, as pointed in your post #2, that consisted of line #570 to #1359.
There seems no book for analyzing the code, for any particular functionality.
No website even.
Would soon start asking questions on the same code fragment.
obviously there is no book. It is a special program, nobody wrote a book about it. If you are interested you need to read the official documentation which is the code itself, containing some comments about the functionality.
From the other hand good c practice and knowledge is required to understand it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
