Sorry, the syntax in my previous mail was not correct. The following should
work:
# other OpenWRT/LEDE configurations
openwisp2fw_source_other_configs:
# busybox
- CONFIG_BUSYBOX_CUSTOM=y
- CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVEHISTORY=y
- CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVE_ON_EXIT=y
- CONFIG_BUSYBOX_CONFIG_FEATURE_REVERSE_SEARCH=y
- CONFIG_BUSYBOX_CONFIG_FEATURE_VI_UNDO=y
- CONFIG_BUSYBOX_CONFIG_WATCH=y
# workaround to avoid conflicts between wpad and wpad-mini
- "# CONFIG_PACKAGE_wpad-mini is not set"
# workaround to compile GL-MT300A
- 'CONFIG_TARGET_SUBTARGET="mt7620"'
- 'CONFIG_TARGET_PROFILE="DEVICE_gl-mt300a"'
Federico
On Thursday, February 2, 2017 at 2:38:43 PM UTC+1, Federico Capoano wrote:
>
> Argh, you hit on the same problem I hit a week ago:
> https://github.com/openwisp/ansible-openwisp2-imagegenerator/issues/3
>
> It is not possible to specify subtargets and specific profiles yet. I have
> to implement this.
>
> I was thinking of introducing a new variable that would deprecate the old
> one, something like:
>
> openwisp2fw_source_targets:
> - board: ar71xx
> subtarget: Generic
> profile: Default
> - board: ramips
> subtarget: ramips_mt7620
> profile: ramips_mt7620_XIAOMI-MIWIFI-MINI
> - board: ramips
> subtarget: ramips_mt7620
> profile: DEVICE_gl-mt300a
>
> The entire process could become more complex, so I have to find the time
> to test this idea a bit and implement it.
>
> For the moment I think you can workaround this issue in two ways:
>
> 1. manual
> compile the default target, go in the source directory and proceed
> manually with a make menuconfig and proceed to select your desired target
>
> 2. ugly temporary workaround
> you could try using the variable *openwisp2fw_source_other_configs* in
> the following way:
>
> # other OpenWRT/LEDE configurations
> openwisp2fw_source_other_configs:
> # busybox
> - CONFIG_BUSYBOX_CUSTOM=y
> - CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVEHISTORY=y
> - CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVE_ON_EXIT=y
> - CONFIG_BUSYBOX_CONFIG_FEATURE_REVERSE_SEARCH=y
> - CONFIG_BUSYBOX_CONFIG_FEATURE_VI_UNDO=y
> - CONFIG_BUSYBOX_CONFIG_WATCH=y
> # workaround to avoid conflicts between wpad and wpad-mini
> - "# CONFIG_PACKAGE_wpad-mini is not set"
> # workaround to compile GL-MT300A
> CONFIG_TARGET_SUBTARGET="mt7620"
> CONFIG_TARGET_PROFILE="DEVICE_gl-mt300a"
>
> I am sorry you had to go through all of this to find out about this issue,
> but now that I know that I'm not the only one facing this issue I will be
> more motivated to fix it in the short term.
>
> Federico
>
>
> On Thu, Feb 2, 2017 at 1:14 PM Xavier Maysonnave wrote:
>
>> Hi Federico,
>>
>> I have built a while ago a LEDE firmware for my device a GL-MT300A, I use
>> it as a reference, especially the content of the .config file.
>>
>> This one contains the following:
>>
>> CONFIG_TARGET_BOARD="ramips"
>> CONFIG_TARGET_SUBTARGET="mt7620"
>> CONFIG_TARGET_PROFILE="DEVICE_gl-mt300a"
>>
>> My playbook contains the following:
>>
>> openwisp2fw_source_archs:
>> - ramips
>>
>> I made many tests but I don't know how to specify the subtarget and the
>> profile ?
>>
>> Thanks
>>
>>
>>
>> Le jeudi 2 février 2017 17:37:23 UTC+5:30, Federico Capoano a écrit :
>>>
>>> That's great news!
>>>
>>> While developing the ansible image generator, I tried setting LEDE as
>>> the default but I couldn't compile successfully most of the time so I had
>>> to switch back to OpenWRT.
>>>
>>> When the LEDE stable will be out, if we like it more than OpenWRT, I'd
>>> be happy to switch the image generator to use the new LEDE stable as
>>> default.
>>>
>>> Federico
>>>
>>>
>>> On Thursday, February 2, 2017 at 12:56:43 PM UTC+1, Xavier Maysonnave
>>> wrote:
>>>>
>>>> Hi Federico,
>>>>
>>>> I switched to the LEDE project as their 17.01.RC1 is out.
>>>> I didn't face the previous crash, now I try to build for my real target
>>>> a GL-MT300A.
>>>> I'll provide feedback.
>>>>
>>>> Thanks
>>>>
>>>> Le samedi 28 janvier 2017 16:44:32 UTC+5:30, Xavier Maysonnave a écrit :
>>>>>
>>>>> Hi All,
>>>>>
>>>>> I started to experiment the image generator following the Readme.md
>>>>> and faces some questions :
>>>>>
>>>>> 1 - in the hosts file I specified an IP address instead of '
>>>>> mycompiler.mydomain.com'
>>>>> However in the playbook.yml file at the beginning there is :
>>>>> - hosts: your_host_here
>>>>> I assume we need also to reference 'mycompiler.mydomain.com'
>>>>> That way we can organize multiple compiler servers if needed ?
>>>>>
>>>>> 2 - I don't understand how the root_password is encrypted as I do not
>>>>> see any salt in the playbook.yml except the one described in the
>>>>> luci_openwisp entry.
>>>>>
>>>>> 3 - Is there somewhere an exhaustive list of variables we can use,
>>>>> it's a little bit magic for me :-)
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
