-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixing fixed length address bug #1
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cesspit
pushed a commit
that referenced
this pull request
Dec 16, 2011
fixing fixed length address bug
frlan
pushed a commit
to frlan/geany-plugins
that referenced
this pull request
Mar 30, 2012
…tion GeanyMacro: Change Wording a little as selection will most likle getting...
cesspit
pushed a commit
that referenced
this pull request
Jun 16, 2012
Various C89-related and other fixes
kugel-
added a commit
to kugel-/geany-plugins
that referenced
this pull request
Jul 28, 2015
This and the following commits are done in two steps Step geany#1 is completely scripted doing the following: for each plugin do mv Makefile.am Makefile.rel.am apply small mods to Makefile.rel.am[1] echo $template > Makefile.am[2] cd src mv Makefile.am Makefile.rel.am apply small mods to Makefile.rel.am echo $template > Makefile.am[2] end [1]: Wrap the contents within if ENABLE_XXX (this is needed due to an autotools limitation, see note about foo_SHORTNAME below) and add an include src/Makefile.rel.am. [2] $plugin/Makefile.am and $plugin/src/Makefile.am are all the same and require no maintance at all. Step geany#2 is done by hand, doing the following for each plugin do apply %D% / %C% to $plugin/src/Makefile.rel.am [3] define %C%_foo_SHORTNAME if necessary[4] [3]: These very modifications are the key part of super-recursive automake. This uses the reldir feature of automake 1.14+. They allow the Makefile.rel.am to be included by the top-level Makefile.am as well as by supdir Makefile.ams. [4]: foo_SHORTNAME is necessary so that running make in the root builds the same .lo files that make in a subdir does (make -C $plugin or make -C $plugin/src). Otherwise automake encodes the directory part into the prefix of the .lo files. Unforunately foo_SHORTNAME is not supported within conditional statements. That's why it has to be outside if ENABLE_FOO ... endif. This is also the reason that fragments are uncluded unconditionally. The definition of foo_SHORTNAME is only necessary if there are target specific rules (e.g. foo_CFLAGS).
kugel-
added a commit
to kugel-/geany-plugins
that referenced
this pull request
Oct 30, 2015
This and the following commits are done in two steps Step geany#1 is completely scripted doing the following: for each plugin do mv Makefile.am Makefile.rel.am apply small mods to Makefile.rel.am[1] echo $template > Makefile.am[2] cd src mv Makefile.am Makefile.rel.am apply small mods to Makefile.rel.am echo $template > Makefile.am[2] end [1]: Wrap the contents within if ENABLE_XXX (this is needed due to an autotools limitation, see note about foo_SHORTNAME below) and add an include src/Makefile.rel.am. [2] $plugin/Makefile.am and $plugin/src/Makefile.am are all the same and require no maintance at all. Step geany#2 is done by hand, doing the following for each plugin do apply %D% / %C% to $plugin/src/Makefile.rel.am [3] define %C%_foo_SHORTNAME if necessary[4] [3]: These very modifications are the key part of super-recursive automake. This uses the reldir feature of automake 1.14+. They allow the Makefile.rel.am to be included by the top-level Makefile.am as well as by supdir Makefile.ams. [4]: foo_SHORTNAME is necessary so that running make in the root builds the same .lo files that make in a subdir does (make -C $plugin or make -C $plugin/src). Otherwise automake encodes the directory part into the prefix of the .lo files. Unforunately foo_SHORTNAME is not supported within conditional statements. That's why it has to be outside if ENABLE_FOO ... endif. This is also the reason that fragments are uncluded unconditionally. The definition of foo_SHORTNAME is only necessary if there are target specific rules (e.g. foo_CFLAGS).
kugel-
added a commit
to kugel-/geany-plugins
that referenced
this pull request
Nov 16, 2015
This and the following commits are done in two steps Step geany#1 is completely scripted doing the following: for each plugin do mv Makefile.am Makefile.rel.am apply small mods to Makefile.rel.am[1] echo $template > Makefile.am[2] cd src mv Makefile.am Makefile.rel.am apply small mods to Makefile.rel.am echo $template > Makefile.am[2] end [1]: Wrap the contents within if ENABLE_XXX (this is needed due to an autotools limitation, see note about foo_SHORTNAME below) and add an include src/Makefile.rel.am. [2] $plugin/Makefile.am and $plugin/src/Makefile.am are all the same and require no maintance at all. Step geany#2 is done by hand, doing the following for each plugin do apply %D% / %C% to $plugin/src/Makefile.rel.am [3] define %C%_foo_SHORTNAME if necessary[4] [3]: These very modifications are the key part of super-recursive automake. This uses the reldir feature of automake 1.14+. They allow the Makefile.rel.am to be included by the top-level Makefile.am as well as by supdir Makefile.ams. [4]: foo_SHORTNAME is necessary so that running make in the root builds the same .lo files that make in a subdir does (make -C $plugin or make -C $plugin/src). Otherwise automake encodes the directory part into the prefix of the .lo files. Unforunately foo_SHORTNAME is not supported within conditional statements. That's why it has to be outside if ENABLE_FOO ... endif. This is also the reason that fragments are uncluded unconditionally. The definition of foo_SHORTNAME is only necessary if there are target specific rules (e.g. foo_CFLAGS).
frlan
pushed a commit
that referenced
this pull request
May 30, 2018
Markdown: Fix a typo in the Makefile.am
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SF bug #3449480