summaryrefslogtreecommitdiff
path: root/interface-definitions/system-proxy.xml.in
AgeCommit message (Collapse)Author
2022-04-29xml: T4047: use full string match in the regex validatorChristian Poessinger
2021-08-17xml: proxy: use port-number building block for system proxyChristian Poessinger
2020-12-12xml: use "u32:" keyword when identifying port rangesChristian Poessinger
This will render the completion help more nicely.
2019-12-10T1843: fix proxy URL handling when running through GCC preprocessorChristian Poessinger
Newer GCC version (8.3 in Debian Buster) no longer support the -ansi option as in GCC 4 used in Debian Jessie. Thus the URL which is used as regex for the proxy must be escaped properly - else the // in the URL is treated as C++ comment.
2019-12-06T1843: run interface-definitions though GCC preprocessorChristian Poessinger
A lot of XML code is duplicated (VLAN, interface address) for instance. Such XML definitions should be moved to feature.xml.i files and then just pulled in via GCC preprocessor #include definition in e.g. bond or ethernet definitions. This will give us the ability to single-source repeating node definitions as: * Interface Address * Interface Description * Interface Disable * VLAN (both vif-s and vif-c) The .in suffix of the interface-definitions is a marker that those files are input files to the GCC preprocessor. They will be rendered into proper XML files in the build directory. Some node definitions have been reworder to remove escaped double quote occurances which would have been warned about by the GCC preprocessor.